If your hosting platform prevents hosting the microsoft-identity-association.json
file in the .well-known
directory, here are some alternative solutions to verify your azure application domain:
DNS Record Verification: Azure supports domain verification using DNS records. Add a TXT record with a specific verification code provided by Azure to your domain's DNS settings. This method does not require hosting files and is compatible with most platforms.
Azure Support Assistance: Reach out to Azure Support and explain the limitation with your hosting platform. While Azure requires the JSON file to be in the .well-known
directory, support might provide guidance or accept your alternative hosted URL for verification, though this is not guaranteed.
Switching to a Proxy Setup: If possible, use a reverse proxy or middleware (e.g., Azure Front Door, Application Gateway) to route requests to the .well-known
path to your custom verification page. This method allows the .well-known
path to be virtually created without modifying your hosting platform's constraints.
Consider Alternate Hosting for Verification: Temporarily switch the domain’s hosting to a platform that supports the .well-known
directory. Once verification is complete, revert to the original hosting provider.
DNS verification is the most straightforward and commonly supported solution. If feasible, prioritize this method to bypass the constraints of your hosting platform.