---
title: Application With Identifier Not Found: Azure Error
description: If you've received the AADSTS700016 error, or something similar, when integrating an application with Azure, here are the steps I've taken to correctly configure the application.
date: 2021-02-22
tags: Azure, SAML, Active Directory Connections
source: https://brianchildress.co/blog/application-with-identifier-not-found-azure-error
---

# Application With Identifier Not Found: Azure Error

I was recently working with [Azure Active Directory (AD)](https://azure.microsoft.com/en-us/services/active-directory/) and [Auth0](https://auth0.com/) for a new [SAML](https://en.wikipedia.org/wiki/Security_Assertion_Markup_Language) (**S**ecurity **A**ssertion **M**arkup **L**anguage) integration. The integration would use Azure AD as the Identity Provider (IdP) and Auth0 as the authorization service provider. To enable the integration I needed to create an [App Registration](https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-register-app) in Azure AD. I won't go into much detail about that process here, creating the App Registration was fairly straightforward.

The error I received was:

![](/src/pages/blog//src/pages/blog/application-with-identifier-not-found-azure-error/azure-app-id-error.png)

> AADSTS700016: Application with identifier '<URN>' was not found in the directory '<TENANT ID>'. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You may have sent your authentication request to the wrong tenant.

For my integration, the Application ID did not match the [URN](https://en.wikipedia.org/wiki/Lex_(URN)) that was generated by Auth0. The error itself makes sense, finding where to update the Application Identifier was not as easy. I'll blame my limited experience with Azure AD and a poor user interface design. Now that I know where to look, it's obvious, at the time, and after much searching I didn't find clear guidance on what to update and where. Here is what I learned.

The Uniform Resource Name (URN) is a unique value assigned by Auth0 to our [Enterprise SAML connection](https://auth0.com/docs/protocols/saml-configuration-options/saml-identity-provider-configuration-settings). I could find the URN in my Auth0 console labeled _Entity ID_:

![](/src/pages/blog//src/pages/blog/application-with-identifier-not-found-azure-error/auth0-entity-id.png)

(I could also find it in the error message I received from Azure 😂) 

The URN value needs to be assigned to the App Registration within our Azure AD console. To access the APP ID, select the _Add an Application ID URI_ option in the Azure AD Console.

![](/src/pages/blog//src/pages/blog/application-with-identifier-not-found-azure-error/azure-add-app-id-link.png)

Within the _Application ID_ view, select the _Set_ option.

![](/src/pages/blog//src/pages/blog/application-with-identifier-not-found-azure-error/azure-ad-set-app-id-link.png)

Update this value with the full URN of your application and select _save_

![](/src/pages/blog//src/pages/blog/application-with-identifier-not-found-azure-error/azure-ad-app-id-form.png)

Now your App Registration in Azure AD _should_ be linked to your application by the URN value.🤞