Expose an API: Registering an static azure web page

Question

HI,

I am trying to follow the steps:
https://learn.microsoft.com/en-us/office/dev/add-ins/develop/register-sso-add-in-aad-v2

I have my static web app hosted at:
https://mycompany.z13.web.core.windows.net/

I am exposing an API using the domain api://mycompany.z13.web.core.windows.net/d3978c06-0636-433b-94bb-c65711c14444

Failed to update Application ID URI application property. Error detail: Values of IdentifierUris property must use a verified domain of the organization or its subdomain

How can I register?

It worked for local host but not for this microsoft azure static web page site. How can I solve? I did not find any documentation

Answer 1

Hi,

Based on the error, the IdentifierUris is not verified in your Azure AD tenant.

IdentifierUris domain needs to be registered and verified in your Azure AD primary domain or subdomain. Check this guide for steps.

https://learn.microsoft.com/en-us/azure/active-directory/enterprise-users/domains-manage

Answer 2

@jrpz
Thank you for your post!

Based off the documentation that you're following, it looks like your scenario isn't supported since You must use a domain that you own. For this reason, you cannot use certain well-known domains such as azurewebsites.net or cloudapp.net.

If you need to purchase a domain using the Azure Portal, you can search for and select App Service Domains -> Select Create. For more info.

Additional Link:
Buying a domain with GoDaddy

Once you purchase the domain you can Add your custom domain name using the Azure Active Directory portal, and re-try following the documentation.

If you have any other questions, please let me know.
Thank you for your time and patience throughout this issue.

----------

Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.

Answer 3

I was wondering what the solution is for those domains? If Microsoft expecting to register custom domains know for every little test machine we create? And what about 3rd party setups in this case? We are using quite a lot of these, don´t need to be mentioned that we can´t add the domain to azure as it does not belong to us. I couldn´t find any explanation or solution for that use case. In general I found this change poorly communicated. Is anyone having a solution for this case?