AADSTS700016: Application with identifier <Id> was not found in the directory <Company>.

Question

Good morning.

I hope you are well.

When trying to connect with:

Connect-PnPOnline -Url "https://name-admin.sharepoint.com" -Interactive

Or with:

Connect-PnPOnline -Url "https://name-admin.sharepoint.com"

It is throwing the error:

AADSTS700016: Application with identifier <Id> was not found in the directory <Company>. 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.

I verified by accessing the URL https://login.microsoftonline.com/common/adminconsent?client_id=your_client_id with the tenant administrator and it throws the same error.

This error started to occur yesterday. It did not occur last week.

How can I solve the incident?

I hope you can help me.

Thank you very much.

Answer 1

Hi Jairo,

I've been having the exact same issue since today, and came across your post. I've since discovered why we were getting that error message, so thought id let you know in case yours is the same issue.

We've been using a service account for credentials that in turn was using the PnP Management Shell application in Azure.

I updated PnP PowerShell module to the latest and it then gave a much better description of the issue when trying to connect:

As of September 9th, 2024 the option to use the PnP Management Shell app registration for authentication is not available anymore. Refer to https://pnp.github.io/powershell/articles/registerapplication.html on how to register your own application.

So looks like we'll need to register our own Entra ID Application to use with PnP PowerShell instead.
And use something like this:

Connect-PnPOnline -Url $AdminCenterURL -ClientId $ClientID -ClientSecret $ClientSecret

Answer 2

Worked for me.

The link provided in the error message (https://pnp.github.io/powershell/articles/registerapplication.html) provides detailed explanation and steps that need to be performed.

Key message here is:

It has always been a recommended practise to register your own Entra ID Application to use with PnP PowerShell. As of September 9th, 2024, this has become mandatory step. This article will guide you through how to do so.

Answer 3

For me it occurred today, a few hours ago I had successfully connected with Connect-PnPOnline, but now I get this same error. Same machine, user, etc.

Answer 4

having the same issue.

Do you have any recvommendations?