Error: AADSTS500011: The resource principal named '*URL*' was not found in the tenant.

%3CLINGO-SUB%20id%3D%22lingo-sub-886632%22%20slang%3D%22en-US%22%3EError%3A%20AADSTS500011%3A%20The%20resource%20principal%20named%20'*URL*'%20was%20not%20found%20in%20the%20tenant.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-886632%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20trying%20to%20add%20an%20app%20to%20our%20SharePoint%20Online%20site%20using%20the%20template%20from%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fsharepoint%2Fdev%2Fspfx%2Fweb-parts%2Fget-started%2Fbuild-a-hello-world-web-part%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fsharepoint%2Fdev%2Fspfx%2Fweb-parts%2Fget-started%2Fbuild-a-hello-world-web-part%3C%2FA%3E%26nbsp%3Band%20we%20get%20the%20error%20below%20when%20we%20deploy%20to%20SharePoint%20and%20add%20the%20app%2FWebpart%20to%20a%20test%20SharePoint%20site.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EFound%20%5Bobject%20Object%5DDriver%20Display%20External%20Error%3A%20Error%3A%20AADSTS500011%3A%20The%20resource%20principal%20named%20%3CA%20href%3D%22https%3A%2F%2Fdriverdisplayexternal.azurewebsites.net%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdriverdisplayexternal.azurewebsites.net%3C%2FA%3E%20was%20not%20found%20in%20the%20tenant%20named%207018324c-9efd-4880-809d-b2e6bb1606b6.%20This%20can%20happen%20if%20the%20application%20has%20not%20been%20installed%20by%20the%20administrator%20of%20the%20tenant%20or%20consented%20to%20by%20any%20user%20in%20the%20tenant.%20You%20might%20have%20sent%20your%20authentication%20request%20to%20the%20wrong%20tenant.%20Trace%20ID%3A%20358b22eb-cd2c-4091-b592-5a57cbc21d00%20Correlation%20ID%3A%20ec96d656-1a36-42e2-a2b9-3ff78efc1e2e%20Timestamp%3A%202019-10-01%2016%3A26%3A06Z%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20834px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F134964i54BE674D393DB195%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22CustomAppError.png%22%20title%3D%22CustomAppError.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EWe%20have%20added%20a%20call%20to%20our%20own%20client%20as%20shown%20below.%20We%20are%20not%20sure%20why%20the%20resource%20principal%20was%20not%20found.%20The%20Tenant%20ID's%20match%20and%20things%20seem%20to%20be%20set%20up%20properly%20for%20authentication.%20Has%20anyone%20else%20encountered%20this%20issue%20or%20know%20where%20to%20look%20for%20the%20issue%3F%20Thanks%20in%20advance!%3C%2FP%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FDIV%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20894px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F134963iE13293151678541B%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22CustomAppError2.png%22%20title%3D%22CustomAppError2.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20804px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F134965i7356906060471F9C%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22CustomAppError3.png%22%20title%3D%22CustomAppError3.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20957px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F134966i72C097DBAAF7B01A%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22CustomAppError4.png%22%20title%3D%22CustomAppError4.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-886632%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EActive%20Directory%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAPI%20Management%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAzure%20AD%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWebPart%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-887037%22%20slang%3D%22en-US%22%3ERe%3A%20Error%3A%20AADSTS500011%3A%20The%20resource%20principal%20named%20'*URL*'%20was%20not%20found%20in%20the%20tenant.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-887037%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20more%20information%20is%20needed%2C%20please%20let%20me%20know%20what%20would%20help%20find%20the%20issue.%20Thanks%20in%20advance!%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

We are trying to add an app to our SharePoint Online site using the template from https://docs.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/get-started/build-a-hello-world-web-p... and we get the error below when we deploy to SharePoint and add the app/Webpart to a test SharePoint site.

 

Found [object Object]Driver Display External Error: Error: AADSTS500011: The resource principal named https://driverdisplayexternal.azurewebsites.net was not found in the tenant named 7018324c-9efd-4880-809d-b2e6bb1606b6. 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 might have sent your authentication request to the wrong tenant. Trace ID: 358b22eb-cd2c-4091-b592-5a57cbc21d00 Correlation ID: ec96d656-1a36-42e2-a2b9-3ff78efc1e2e Timestamp: 2019-10-01 16:26:06Z

 

CustomAppError.png

We have added a call to our own client as shown below. We are not sure why the resource principal was not found. The Tenant ID's match and things seem to be set up properly for authentication. Has anyone else encountered this issue or know where to look for the issue? Thanks in advance!

 

CustomAppError2.png

CustomAppError3.png

 

CustomAppError4.png

1 Reply
Highlighted

If more information is needed, please let me know what would help find the issue. Thanks in advance!