-
Notifications
You must be signed in to change notification settings - Fork 100
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
[MissingPortal] No Team Admin Centers are Listed #249
Comments
Any idea what these URLs might be? |
Looks like this may have been resolved at some point already. https://msportals.io/usgovt?search=Teams Really, everything needs to get rearranged, because I don't believe that "GCC Moderate" is an ACTUAL thing as much as a slang term for "GCC" that doesn't need the ".us" URLs from GCC High, and don't need the DoD cloud. The line between GCC and Azure Government can also be somewhat confusing because people try to differentiate "onmicrosoft.us" as "Azure Government", but you can also have GCC (non High) running in Azure Commercial. This really brings up like four levels of Portal differentiation, possibly additional for specialized uses (that we don't have access to
|
So, there are a BUNCH of categories that I don't believe ACTUALLY exist on the page currently
So I am thinking these should be restructured, perhaps like below, based on the URLs So, really, I believe that the "Government" pages should merge to
For example, here are a number of URLs for Power Platform - https://learn.microsoft.com/en-us/power-platform/admin/powerapps-us-government#power-apps-us-government-service-urls Where you can see for example that it changes around these levels
It gets confusing though, because "GCC" for Defender XDR seems to say to use the same URL as Commercial
|
You write a convincing argument @PsychoData :) Wanna make the changes by any chance? |
Portal Name
Teams Admin for GCC High and GCC Mod
Portal URL
Secondary Portal URLs
What portal page and section would this fit best on?
Special Notes
Additional context
The text was updated successfully, but these errors were encountered: