Error provisioning for a single non-admin user

[azure-samples]

Error provisioning for a single non-admin user

[grzewal]

Hi!

I had this same problem and was able to resolve it. In the NEW portal you need to edit the manifest of the native application and set "availableToOtherTenants" flag to true. By default the NEW portal sets it to false (the old portal used to set it to true by default).

HTH

[sanchezpablo]

I'm having the same problem using NEW azure portal, when I register a new native application with all the permissions needed and I try to obtain the access token using:

        AuthenticationResult authResult = null;
        string resource = "https://management.core.windows.net/";
        var authenticationContext = new AuthenticationContext("https://login.windows.net/" + tenantId);
        try
        {
            authResult = authenticationContext.AcquireToken(resource,
                appId,
                new UserCredential(
                    partnerCenterUser,
                    partnerCenterPassword
                )
            );
        }
        catch (Exception ex)
        {
            throw;
        }
        return authResult;

I obtain the error message:

AADSTS70001: Application with identifier '4f7d5168-f754-42ed-a43d-1f0363ede30e' was not found in the directory tenantresellernew30.onmicrosoft.com
Trace ID: 182d19d7-68a7-4a48-bee1-f87486d31c66
Correlation ID: 75ef5bbb-06f9-4a06-a384-45860dae2568
Timestamp: 2016-10-13 07:32:25Z

I'm using sandbox account to perform the tests, but also in production we are facing this problem.

Any help is welcome because we are stucked and we need to integrate azure in our multi-tenant environment.

[dstrockis]

Hey Darek. Is the application XXX set as a multi-tenant application in the azure portal?

What was the domain of the user you attempted to sign in as? Was it YYY.onmicrosoft.com?

[dgrala]

Yes and yes.

Provisioning with an admin account works.

Sent from my Windows Phone

---

From: Danny Strockismailto:[email protected]
Sent: ‎4/‎16/‎2015 10:11 AM
To: AzureADSamples/WebApp-MultiTenant-OpenIdConnect-DotNetmailto:[email protected]
Cc: Darek Gralamailto:[email protected]
Subject: Re: [WebApp-MultiTenant-OpenIdConnect-DotNet] Error provisioning for a single non-admin user (#8)

Hey Darek. Is the application XXX set as a multi-tenant application in the azure portal?

What was the domain of the user you attempted to sign in as? Was it YYY.onmicrosoft.com?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/8#issuecomment-93787336.

[dstrockis]

Does tenant YYY allow regular users to consent to applications? There is a config switch to set this on the Configure tab of the tenant in the Azure portal.

If that switch is set correctly, please provide a correlationId and timestamp for the error and I can take a deeper look.

[dgrala]

Thanks, I checked the settings and they should be able to consent.

Additional technical information:

Correlation ID: 98b9b314-b558-430d-a0e1-790459bad062

Timestamp: 2015-04-16 06:10:49Z

AADSTS70001: Application with identifier d0a17f8c-4463-47c2-ae03-04601528c5a3 was not found in the directory fbtest.onmicrosoft.com

From: Danny Strockis [mailto:[email protected]]
Sent: Thursday, April 16, 2015 11:28 AM
To: AzureADSamples/WebApp-MultiTenant-OpenIdConnect-DotNet
Cc: Darek Grala
Subject: Re: [WebApp-MultiTenant-OpenIdConnect-DotNet] Error provisioning for a single non-admin user (#8)

Does tenant YYY allow regular users to consent to applications? There is a config switch to set this on the Configure tab of the tenant in the Azure portal.

If that switch is set correctly, please provide a correlationId and timestamp for the error and I can take a deeper look.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/8#issuecomment-93808710.

[dgrala]

Ping

[karenpliu]

I have the same problem, does anyone have clue?

[monubamb]

Thanks that helped resolve the problem

[bforsyt4]

Thanks that worked for me.

[kalyankrishna1]

The sample has been heavily updated, including steps

• register and consent the apps in multiple tenants
• to deploy this in the sovereign clouds.
• to deploy this on Azure
  Please give the updated the sample a try and let us know on this thread if you have more issues.