Skip to content

Commit edc9573

Browse files
authored
Merge pull request #107613 from Heidilohr/work-tabs-freshness
Changed all mentions of "blades" to "tabs" based on freshness update
2 parents 5324e40 + 3dd965d commit edc9573

File tree

4 files changed

+6
-6
lines changed

4 files changed

+6
-6
lines changed

articles/virtual-desktop/create-fslogix-profile-container.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ To get started, you need to set up an Azure NetApp Files account.
6868
7. Select **Azure NetApp Files** in the search results, then select **Create**.
6969

7070
8. Select the **Add** button.
71-
9. When the **New NetApp account** blade opens, enter the following values:
71+
9. When the **New NetApp account** tab opens, enter the following values:
7272

7373
- For **Name**, enter your NetApp account name.
7474
- For **Subscription**, select the subscription for the storage account you set up in step 4 from the drop-down menu.
@@ -87,7 +87,7 @@ Next, create a new capacity pool:
8787
1. Go to the Azure NetApp Files menu and select your new account.
8888
2. In your account menu, select **Capacity pools** under Storage service.
8989
3. Select **Add pool**.
90-
4. When the **New capacity pool** blade opens, enter the following values:
90+
4. When the **New capacity pool** tab opens, enter the following values:
9191

9292
- For **Name**, enter a name for the new capacity pool.
9393
- For **Service level**, select your desired value from the drop-down menu. We recommend **Premium** for most environments.
@@ -122,7 +122,7 @@ Next, you'll need to create a new volume.
122122

123123
1. Select **Volumes**, then select **Add volume**.
124124

125-
2. When the **Create a volume** blade opens, enter the following values:
125+
2. When the **Create a volume** tab opens, enter the following values:
126126

127127
- For **Volume name**, enter a name for the new volume.
128128
- For **Capacity pool**, select the capacity pool you just created from the drop-down menu.

articles/virtual-desktop/expand-existing-host-pool.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ Here's how to redeploy the Azure Resource Manager template to expand a host pool
6666

6767
## Run the Azure Marketplace offering
6868

69-
Follow the instructions in [Create a host pool by using the Azure Marketplace](./create-host-pools-azure-marketplace.md) until you reach [Run the Azure Marketplace offering to provision a new host pool](./create-host-pools-azure-marketplace.md#run-the-azure-marketplace-offering-to-provision-a-new-host-pool). When you get to that point, you'll need to enter the following information for each blade:
69+
Follow the instructions in [Create a host pool by using the Azure Marketplace](./create-host-pools-azure-marketplace.md) until you reach [Run the Azure Marketplace offering to provision a new host pool](./create-host-pools-azure-marketplace.md#run-the-azure-marketplace-offering-to-provision-a-new-host-pool). When you get to that point, you'll need to enter the following information for each tab:
7070

7171
### Basics
7272

articles/virtual-desktop/tenant-setup-azure-active-directory.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ To assign the TenantCreator application role:
7777
3. Select **Users and groups**. You might see that the administrator who granted consent to the application is already listed with the **Default Access** role assigned. This is not enough to create a Windows Virtual Desktop tenant. Continue following these instructions to add the **TenantCreator** role to a user.
7878
7979
![A screenshot of the users and groups assigned to manage the "Windows Virtual Desktop" enterprise application. The screenshot shows only one assignment, which is for "Default Access."](media/tenant-default-access.png)
80-
4. Select **Add user**, and then select **Users and groups** in the **Add Assignment** blade.
80+
4. Select **Add user**, and then select **Users and groups** in the **Add Assignment** tab.
8181
5. Search for a user account that will create your Windows Virtual Desktop tenant. For simplicity, this can be the global administrator account.
8282
- If you're using a Microsoft Identity Provider like [email protected] or [email protected], you might not be able to sign in to Windows Virtual Desktop. We recommend using a domain-specific account like [email protected] or [email protected] instead.
8383

articles/virtual-desktop/troubleshoot-set-up-issues.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -140,7 +140,7 @@ Example of raw error:
140140

141141
To fix this, do the following things:
142142

143-
1. Open the Azure Portal and go to the **Virtual networks** blade.
143+
1. Open the Azure Portal and go to the **Virtual networks** tab.
144144
2. Find your VNET, then select **DNS servers**.
145145
3. The DNS servers menu should appear on the right side of your screen. On that menu, select **Custom**.
146146
4. Make sure the DNS servers listed under Custom match your domain controller or Active Directory domain. If you don't see your DNS server, you can add it by entering its value into the **Add DNS server** field.

0 commit comments

Comments
 (0)