Skip to content

Document Microsoft Teams infrastructure locations for GCC High#13928

Closed
tsweatman1 wants to merge 1 commit intoMicrosoftDocs:publicfrom
tsweatman1:patch-1
Closed

Document Microsoft Teams infrastructure locations for GCC High#13928
tsweatman1 wants to merge 1 commit intoMicrosoftDocs:publicfrom
tsweatman1:patch-1

Conversation

@tsweatman1
Copy link

Added information about Microsoft Teams infrastructure locations for GCC High Gov cloud.

One of our large USGOV cloud customers, RTX, is requesting we update our Microsoft documentation to reflect that our Teams infrastructure for USGOV cloud is not located in region USGOV Virginia and only in USGOV Texas and Arizona.

They would simply like a 'Note' stating as such for their training purposes. Through Kusto querying they noted all routing for Media Processors travel to AZ and TX only.

Added information about Microsoft Teams infrastructure locations for GCC High Gov cloud.

One of our large USGOV cloud customers, RTX, is requesting we update our Microsoft documentation to reflect that our Teams infrastructure for USGOV cloud is not located in region USGOV Virginia and only in USGOV Texas and Arizona.
 
They would simply like a 'Note' stating as such for their training purposes.  Through Kusto querying they noted all routing for Media Processors travel to AZ and TX only.
@github-actions
Copy link

Thank you for your contribution! To reduce the chances of pre-release content being released publicly, and to simplify the contribution workflow, Microsoft FTEs and vendors must submit contributions to private repositories. Private repositories typically have the same name as public repositories with the -pr suffix added.

For example, if the public repository name is contoso-help, the private repository name is usually contoso-help-pr.

Please re-submit your contribution to the private repository. If you can’t find the private repository to use, do one of the following:

  • (Preferred) Go to https://aka.ms/SaveTime and paste the public Learn (not GitHub) URL of the page you want to update into the field provided. If you haven't used the Learn Editor before, check out the Learn Editor documentation. If you see a 404, be sure to sign into Learn by clicking Sign in in the top-right corner of the page.
  • Install the Microsoft Learn maintenance tool browser extension and, while on the article you want to update, click the extension in the toolbar, then choose MD or YML.
  • Retrieve the article source URL from page source:
    1. Right-click on the article page and select View source.
    2. Find original_content_git_url and paste that URL into the address bar of a new tab.
    3. Switch the branch to main.
    4. Click Edit and follow the steps to update the article.

If you have questions or need help, please post a message to G+E LMC Support (aka AskAnAdmin) (Microsoft FTE or vendor login required).

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 607b03e:

✅ Validation status: passed

File Status Preview URL Details
microsoft-365/enterprise/microsoft-365-u-s-government-gcc-high-endpoints.md ✅Succeeded

For more details, please refer to the build report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant