How to Migrate Plesk DNS Records from Amazon to Azure
Question details
The user needs to properly migrate and recreate Plesk DNS records, particularly Microsoft 365 SRV records, after moving their server infrastructure from Amazon (AWS) to Azure.
- Product
- Plesk DNS / Microsoft 365
- Device & OS
- not provided
- Scenario
- Migrating a Plesk hosting environment from Amazon Web Services (AWS) to Microsoft Azure, which breaks previous automatic DNS integrations.
- Observed behavior
- Microsoft 365 DNS records do not migrate automatically, requiring manual recreation. Specific SRV records need exact values for service, protocol, priority, weight, port, and target, which sometimes fail to populate in the new interface.
Ensure you have administrative access to your new Azure Plesk panel, access to your authoritative DNS provider, and a complete backup or export of your existing AWS DNS zone files for accurate reference.
Recreate Microsoft 365 DNS and SRV Records in the Plesk Interface
Use this method to manually input specific values for SRV and other Microsoft 365 records directly into your new Azure-hosted Plesk environment.
Manual recreation is the safest way to ensure complex Microsoft 365 records, particularly SRV types, are mapped to the correct fields in the new Azure Plesk environment.
Log in to your Azure Plesk Admin panel, navigate to 'Websites & Domains', select the relevant domain, and click on 'DNS Settings'.
Click 'Add Record' to begin recreating your Microsoft 365 DNS entries based on your AWS export.
Select 'SRV' as the record type. Carefully input the service, protocol, priority, weight, port, and target values exactly as required by Microsoft 365.
Click 'OK' to save the record, then click 'Update' in the yellow alert box to apply the changes to the authoritative DNS zone.
Automate Bulk DNS Record Creation using the Plesk API
Ideal for server administrators managing multiple domains or large batches of Microsoft 365 records, allowing you to script the migration process.
Manage Your Server Migration Plans with WPS Office
Tenant migrations involving AWS, Azure, and Microsoft 365 DNS require careful planning and documentation. While WPS Office cannot configure server DNS, it serves as an excellent, lightweight alternative to Microsoft Office for writing migration scripts, documenting server settings, and collaborating with your IT team.
- 1. Download and Install: Visit the official WPS website, download the free suite, and run the lightweight installer.
- 2. Open Migration Documents: Drag and drop your existing Microsoft Office migration plans or CSV zone files into WPS Office to view and edit them.
- 3. Collaborate and Save: Edit your server configuration checklists and save them in standard Office formats to share with your systems administrators.
Frequently Asked Questions
Why didn't my Microsoft 365 DNS records migrate automatically from AWS to Azure?
When migrating a Plesk environment across different cloud infrastructure providers (from AWS to Azure), automatic DNS integration tools often reset or fail to carry over custom zone files due to different backend network routing, requiring manual intervention or API scripting.
What values are required to properly recreate a Microsoft 365 SRV record in Plesk?
To correctly route Microsoft 365 services, an SRV record requires specific parameters: the Service (e.g., _sip), Protocol (e.g., _tls), Priority, Weight, Port, and Target destination.
What should I do if the Plesk interface doesn't accept my SRV protocol values?
If the Plesk DNS interface restricts or hides specific fields for SRV records, you should temporarily bypass Plesk and add the SRV records directly via your domain registrar's DNS management panel, or contact Plesk Support for a resolution.
Can I use a zone file import to migrate DNS from Amazon to Azure Plesk?
While Plesk supports some zone file imports, complex Microsoft 365 SRV records sometimes fail validation during bulk import. It is often recommended to use the Plesk API or manual entry for precise control over field mapping.
