-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Authenticating to National Cloud Deployments #396
Comments
Adding an example of how PowerShell currently supports national clouds https://review.learn.microsoft.com/en-us/graph/sdks/national-clouds?branch=main&tabs=powershell#tabpanel_1_powershell |
We will be implementing this feature by doing the following:
|
@sebastienlevert, Petr is asking about the acceptance criteria around cloud names. What names should the user type into the CLI for each cloud? I'd planned on using:
|
I'd go with the same as PowerShell, aka
These should be validated and be the only entries avaulabk, like an enum. Default is Global. |
Allows logging in to national clouds using the `--environment` CLI option. See microsoftgraph/msgraph-cli#396
feat: add national cloud support Allows logging in to national clouds using the `--environment` CLI option. See microsoftgraph/msgraph-cli#396 perf: enable concurrent io when clearing the token cache
Added in #423. Should be part of v1.3.0 |
release 1.3.0 is out. |
@ellisgeek, could you confirm if this issue is fixed for you? |
I work for an organization on a GCC High Tenant and would like to be able to use the graph cli for various tasks but it appears that there is no support for authenticating to national cloud deployments at this time. I was unable to locate any referenced to national cloud or microsoft.us in the repository and received the following error and stack trace when attempting to authenticate against my tenant.
The text was updated successfully, but these errors were encountered: