Skip to content

Commit 19e9031

Browse files
committed
list fixes
1 parent f505ad6 commit 19e9031

1 file changed

Lines changed: 17 additions & 17 deletions

File tree

windows-365/enterprise/set-up-tenants-windows-365-gcc.md

Lines changed: 17 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -59,24 +59,24 @@ If you want to use Azure AD join or hybrid Azure AD join, consider these prepara
5959

6060
**Hybrid Azure AD joined Cloud PCs**: If you want to use a hybrid Azure AD join infrastructure, you'll need to configure your commercial (.com) tenant and your government (.us) tenants before creating your Azure Virtual Networks.
6161

62-
## Mapping the commercial and government tenants
62+
## Map the commercial and government tenants
6363
For the two tenants to be connected and have the ability for a user with an identity in the Azure Commercial cloud to access their Windows 365 Cloud PCs provisioned in the Azure Government, the Tenant Mapping PowerShell script will need to be run. The mapping also enables administrators using their Azure Commercial identity to provision and manage the Windows 365 Cloud PCs in the Azure Government cloud.
6464

6565
1. Find the following information. It will be used later in these steps.
66-
- [Commercial Azure tenant ID](/azure/active-directory/fundamentals/active-directory-how-to-find-tenant).
67-
- Commercial Azure Global administrator user name and password.
68-
- [Azure Government tenant ID](/azure/active-directory/fundamentals/active-directory-how-to-find-tenant).
66+
- [Commercial Azure tenant ID](/azure/active-directory/fundamentals/active-directory-how-to-find-tenant).
67+
- Commercial Azure Global administrator user name and password.
68+
- [Azure Government tenant ID](/azure/active-directory/fundamentals/active-directory-how-to-find-tenant).
6969
- Azure Government Global administrator credentials user name and password.
7070
2. Make sure you have Windows PowerShell version 5.1. Other versions may result in errors when running the script.
7171
3. Go to the [Windows 365 PowerShell GitHub repository](https://github.com/microsoft/Windows365-PSScripts).
7272
4. Navigate to the **Windows 365 GCC** folder > right-click **TenantMapping.ps1** > **Save link as** > save the file to a location on your computer.
7373
5. Open Windows PowerShell 5.1 and run the PowerShell script.
74-
>[!NOTE]
75-
>If the script was previously run successfully, you'll see the error **HttpStatusCode Conflict**. This warning can be ignored to execute the script functions Add and Get.
74+
>[!NOTE]
75+
>If the script was previously run successfully, you'll see the error **HttpStatusCode Conflict**. This warning can be ignored to execute the script functions Add and Get.
7676
6. In PowerShell 5.1, type **I** to initiate tenant mapping.
7777
7. After the Initialization completes, type **A** at the prompt. When prompted, type the following information:
78-
- Your Commercial tenant ID, which can be found here: https://portal.azure.com/.
79-
- Your Azure Government tenant ID, which can be found here: https://portal.azure.us/.
78+
- Your Commercial tenant ID, which can be found here: https://portal.azure.com/.
79+
- Your Azure Government tenant ID, which can be found here: https://portal.azure.us/.
8080
8. When prompted, press Enter to open a web browser and enter your user name and password for your commercial tenant ([email protected]).
8181
9. When prompted, press Enter to open a web browser and enter your credentials for your Azure government tenant ([email protected]).
8282
10. After the mapping completes, you'll see **Added tenant mapping successfully!**
@@ -101,20 +101,20 @@ You will need Commercial and Gov credentials and line of sight to both tenants t
101101
When provisioning Windows 365 Cloud PCs without the Microsoft Hosted Network (MHN), you must define an Azure Network Connection (ANC) resource that the Cloud PCs will use to connect with other resources, including your on-prem infrastructure. This will allow GCC customers to use their own network. There is also an option to enable customers to use custom images when the Windows 365 Cloud PCs are provisioned.
102102

103103
1. Gather the following information. It will be used later in these steps.
104-
- Commercial Azure tenant ID.
105-
- Commercial Azure Global administrator username and password.
106-
- Azure Government tenant ID.
107-
- Azure Government Global administrator credentials username and password.
108-
- Subscription in the Azure Government tenant.
109-
- Resource Group in the Azure Government tenant.
110-
- Virtual Network in the Azure Government tenant.
104+
- Commercial Azure tenant ID.
105+
- Commercial Azure Global administrator username and password.
106+
- Azure Government tenant ID.
107+
- Azure Government Global administrator credentials username and password.
108+
- Subscription in the Azure Government tenant.
109+
- Resource Group in the Azure Government tenant.
110+
- Virtual Network in the Azure Government tenant.
111111
2. Make sure you have Windows PowerShell version 5.1. Other versions may result in errors when running the script.
112112
3. Go to the [Windows 365 PowerShell GitHub repository](https://github.com/microsoft/Windows365-PSScripts).
113113
4. Navigate to the **Windows 365 GCC** folder > right-click **GrantSPRolesInTenant.ps1** > **Save link as** > save the file to a location on your computer.
114114
5. Open Windows PowerShell 5.1 and run the PowerShell script. First step is to login to your Azure Government cloud tenant.
115115
6. At the prompt, type one of the following options:
116-
- **2** to grant permissions to create Azure Network Connections (ANC).
117-
- **3** to grant permissions to create ANCs and upload custom images.
116+
- **2** to grant permissions to create Azure Network Connections (ANC).
117+
- **3** to grant permissions to create ANCs and upload custom images.
118118
7. The script lists the subscriptions available for the Azure Government cloud tenant. Select the subscription that you want to use.
119119
8. The resource groups for that subscription are listed. Select the group that you want to use.
120120
9. Select your vNet.

0 commit comments

Comments
 (0)