Personal and Microsoft Accounts are not supported for Azure DNS. Only Azure Active Directory (AAD) organizational accounts (also known as ‘Work or School Accounts’) are supported.
If you try to manage an Azure DNS / Key Vault with a MSA account you will get the following error.
If you signed up for the RCL Portal with a personal Microsoft account (MSA), please follow the instructions in the following link to associate an AAD account to your subscription:
To create certificates for Azure DNS / Key Vault, the Azure AAD organizational account that you use to login to RCL must either be :
An administrator to the subscription containing the Azure DNS Zone(s) / Key Vault(s)
Have a role of ‘Owner’ or ‘Contributor’ to the subscription containing the Azure DNS Zone(s) / Key Vault(s)
If either of these requirements are not met, the ‘subscriptions’, ‘Key Vault’ and ‘DNS Zone’ lists will be empty when you try to create a certificate.
You may also experience an error message.
To set up access control for your AAD account, follow the instructions in the link below :
RCL uses the DNS-01 challenge type to issue certificates for :
- primary domains (e.g. contoso.net)
- subdomains (e.g. store.contoso.net)
- wild card subdomains (e.g. *.contoso.net)
The DNS challenge type ONLY works with an Azure DNS Zone.
If you bought your domain with a domain registrar, you must set up your Azure DNS Zone to manage the records for your domain.
Follow the instructions in the link below to set up your DNS Zone and delegate the name server (NS) records for your domain :
If you do not have an Azure Key Vault, follow the steps in this link to create one :
You must have security access to the Azure Key Vault certificate operations.
If you do not set the access policy for Key Vault, you will experience ‘Access Denied’ or ‘Forbidden’ errors when you try to create a certificate.
This access policy is required to import the SSL/TLS certificate in a Key Vault in your Azure account. If you have not yet created an access policy for your certificates, then follow these steps.
- In your Azure Key Vault, click on the ‘Access policies’ link. Then click on ‘Add Access Policy’.
Select all the permissions for the ‘Certificate permissions’ (select all 16). Ensure you include the purge permission.
Select a service principal : search for the Azure Active Directory organizational account that you use to login to the RCL portal
Click the ‘Select’ button
Click the ‘Add’ button when you are done
The new access policy will be added
Click the ‘Save’ icon at the top to save the access policy
- In the ‘Certificates’ module of the portal, click on the Create New SSL/TLS Certificate link
Select the ‘Azure Key Vault’ option
Add the data to create the certificate. The image below illustrates sample data.
The ‘Host Name’ is the primary domain (eg. contoso.com), subdomain (eg. shop.contoso.com) or wildcard subdomain (eg. *.contoso.com) that your are requesting the SSL/TLS certificate for.
In this case, we are requesting a SSL/TLS certificate for the custom primary domain, ‘shopeneur.com’.
Select the Key Vault name.
The Host Name must be valid for the DNS Zone. For instance, ‘shopeneur.com’, ‘store.shopeneur.com’, ‘*.shopeneur.com’ is valid for the DNS Zone ‘shopeneur.com’
Click the Create Button when you are done
You will need to wait up to 10 mins to validate the site and install the certificate. When this is done, the SSL/TLS certificate will be displayed in the certificates list.
- When this is done, the SSL/TLS certificate will be displayed in the certificates list.
- You can now access your certificate in your Azure Key Vault in the Azure portal.
SSL/TLS certificates will expire in 90 days. You can manually renew a certificate at any point before the expiry date. Click on the ‘Update’ link in the ‘Manage’ menu in the certificates list to update a certificate.
You can use the RCL AutoRenew Function to automatically renew certificates in Azure Key Vault.
Follow the instructions in the link to use the AutoRenew function :
There is a rate limit of 50 SSL/TLS certificates per subscription.
In addition, Let’s Encrypt has instituted rate limits to ensure fair usage by as many people as possible. To find out more about these rate limits please refer to the following link :