topic tenant identifier 'authorize' is neither a valid DNS name, nor a valid external domain error in Developer

tenant identifier 'authorize' is neither a valid DNS name, nor a valid external domain error

SBDEV — Fri, 09 Sep 2022 01:14:58 GMT

Hi,

I'm hoping someone has some ideas, we started having this problem about a week ago. We cannot access https://analysis.windows.net/powerbi/api used for integration to acquire a token.

The error message is:

AADSTS900023: Specified tenant identifier 'authorize' is neither a valid DNS name, nor a valid external domain. Trace ID: 7c84e182-7173-47de-9737-4cc3cebb4700 Correlation ID: b2eabff7-593f-4909-980f-6dfa709310ef Timestamp: 2022-09-02 02:43:25Z

Here is the c# code:

var authenticationContext = new AuthenticationContext("https://login.windows.net/common/oauth2/authorize/");
var authenticationResult = authenticationContext.AcquireTokenAsync("https://analysis.windows.net/powerbi/api", settings.ApplicationId, credential).GetAwaiter().GetResult();

Any advice would be appreciated.

Thanks!

Re: tenant identifier 'authorize' is neither a valid DNS name, nor a valid external domain error

lbendlin — Sat, 10 Sep 2022 20:28:20 GMT

You can raise an issue at https://issues.powerbi.com . If you have a Pro license you can consider raising a Pro ticket at https://powerbi.microsoft.com/en-us/support/pro/

Re: tenant identifier 'authorize' is neither a valid DNS name, nor a valid external domain error

SBDEV — Mon, 12 Sep 2022 01:50:34 GMT

Appreciate the help, I did create a ticket and they suggested I contact the community. They are now going to assign a developer to contact us.

Thanks

Re: tenant identifier 'authorize' is neither a valid DNS name, nor a valid external domain error

limdv1 — Thu, 22 Sep 2022 18:53:58 GMT

Did you ever get a response, I am getting the same error after updating to Microsft.PowerBI.Api v 4.10.0

Re: tenant identifier 'authorize' is neither a valid DNS name, nor a valid external domain error

skuimtor — Fri, 13 Jan 2023 08:33:22 GMT

If this is in a corporate environment, you need to specify the corporate domain you are authenticating against. if my user is joeblogs@contoso123.com ..... use contoso123.com in the tenant field. It worked for me. Hope it helps someone else.