Do you know if there are limitations to using the 365 scope with a .US azure tenant. It seems like the 365 scope only attempts a login at login.microsoftonline.com and there is no way to configure this to be login.microsoftonline.us - is this a correct understanding? If so, is there a way to change it?
@swashburne I don’t have such a tenant to test. But I guess if you specify an Application ID that is part of an .US tenant it should work.
When you register an application in your .US tenant, maybe the default URIs will be http://login.microsoftonline.us/ rather that .com as in my case (see screenshot).
I did test with that URI, but it did not seem to work. I was working with fiddler and I noticed that no matter what combination I used, the UI Path scope still tried to access login.microsoft.com. It also seems like UI Path registers itself as an Enterprise App within the tenant
and I am wondering if it creates a conflict to use the custom app registration versus the enterprise? Also, I did a test using a commercial tenant and it was successful. However, even though I have the gov tenant specified in the sequence, it still redirects to the commercial tenant and seemingly uses the interactive token to log in - is there a cache I need to clear somewhere?
Hi @swashburne I’ve sent you a private message with an alpha version of Office 365 package with added support for national clouds. Please try it and let me know whether it is working for you now.