Microsoft Azure DNS Integartion
Link your Azure DNS account to effortlessly manage your DMARC, SPF, and other email authentication records right from the EasyDMARC dashboard. This integration streamlines the entire process, removing the need for manual updates in the Azure portal and ensuring your records are always accurately configured for maximum security and deliverability.
To enable EasyDMARC to automatically manage the DNS records required for your email security configurations (DMARC, SPF, etc.), you need to grant our application permission to access your Azure DNS zones. This is a secure, two-step process that you control completely.
1. Grant Consent: An administrator must first grant consent, which allows the EasyDMARC application identity to exist within your Azure environment.
2. Assign Permissions: You then assign specific, limited permissions to that application identity, granting it the ability to manage records only in the DNS zones you specify.
Step 1: The Consent and Authorization Process
This initial step creates a secure link between your EasyDMARC account and your Azure tenant.
1. Log in to your EasyDMARC dashboard and navigate to the Azure DNS integration page.
2. Click the "Connect to Microsoft Azure" button. You will be redirected to a Microsoft sign-in page.
3. Sign in using an account with administrative privileges in your Microsoft Entra ID. The required roles are Global Administrator, Application Administrator, or Cloud Application Administrator.
4. After signing in, you will see a permissions request prompt. This prompt will detail the application name ("EasyDMARC DNS Integration") and the publisher. Look for the blue "Verified" badge, which confirms the application's authenticity.
5. Review the requested permissions and click "Accept".
6. You will be redirected back to the EasyDMARC dashboard. The connection status should now indicate that consent has been granted and is "Awaiting Permissions".
Step 2: Assigning DNS Permissions via Azure RBAC
Consenting to the application creates its identity but grants it no rights to manage resources. You must now explicitly assign those rights using Azure Role-Based Access Control (RBAC). The principle of least privilege dictates that permissions should be granted only at the scope necessary. We recommend assigning permissions at the individual DNS Zone level.
Using the Azure Portal
This is the most straightforward method for assigning permissions.