Skip to content

Commit affc461

Browse files
authored
Merge pull request #113009 from Heidilohr/work-overview-edit
Edit to overview page and misc. articles
2 parents 743984c + 4407d85 commit affc461

File tree

4 files changed

+11
-8
lines changed

4 files changed

+11
-8
lines changed

articles/virtual-desktop/connect-windows-7-and-10.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ manager: lizross
1717
You can access Windows Virtual Desktop resources on devices with Windows 7, Windows 10, and Windows 10 IoT Enterprise using the Windows Desktop client.
1818

1919
>[!NOTE]
20-
>The client automatically detects whether you're using the Fall 2019 release or the Spring 2020 release of Windows Virtual Desktop.
20+
>The Windows client automatically defaults to Windows Virtual Desktop Fall 2019 release. However, if the client detects that the user also has Azure Resource Manager resources, it automatically adds the resources or notifies the user that they are available.
2121
2222
> [!IMPORTANT]
2323
> Windows Virtual Desktop doesn't support the RemoteApp and Desktop Connections (RADC) client or the Remote Desktop Connection (MSTSC) client.

articles/virtual-desktop/create-host-pools-powershell.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ This article assumes you've already followed the instructions in [Set up the Pow
2929
Run the following cmdlet to sign in to the Windows Virtual Desktop environment:
3030

3131
```powershell
32-
New-AzWvdHostPool -ResourceGroupName <resourcegroupname> -Name <hostpoolname> -WorkspaceName <workspacename>
32+
New-AzWvdHostPool -ResourceGroupName <resourcegroupname> -Name <hostpoolname> -WorkspaceName <workspacename> -HostPoolType <RemoteApp|Desktop> -Location -DesktopAppGroupName <appgroupname>
3333
```
3434

3535
This will create the host pool, workspace and desktop app group. Additionally, it will register the desktop app group to the workspace. You can only create a workspace with this, not use an existing workspace in this cmdlet.

articles/virtual-desktop/diagnostics-log-analytics.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -123,9 +123,7 @@ You can access Log Analytics workspaces on the Azure portal or Azure Monitor.
123123

124124
4. Follow the instructions in the logging page to set the scope of your query.
125125

126-
5. You are ready to query diagnostics. All diagnostics tables have a "WVD" prefix.
127-
128-
![]()
126+
5. You are ready to query diagnostics. All diagnostics tables have a "WVD" prefix.
129127

130128
## Cadence for sending diagnostic events
131129

articles/virtual-desktop/overview.md

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: Heidilohr
66

77
ms.service: virtual-desktop
88
ms.topic: overview
9-
ms.date: 04/10/2020
9+
ms.date: 04/30/2020
1010
ms.author: helohr
1111
manager: lizross
1212
---
@@ -93,9 +93,12 @@ The Azure virtual machines you create for Windows Virtual Desktop must have acce
9393
|prod.warmpath.msftcloudes.com|443|Agent traffic|AzureCloud|
9494
|catalogartifact.azureedge.net|443|Azure Marketplace|AzureCloud|
9595
|kms.core.windows.net|1688|Windows activation|Internet|
96+
|wvdportalstorageblob.blob.core.windows.net|443|Azure portal support|AzureCloud|
9697

9798
>[!IMPORTANT]
9899
>We recommend you use the service tags instead of URLs in most cases to prevent service issues. Unblocking these URLs is essential for a reliable Windows Virtual Desktop deployment. Blocking access to these URLs is unsupported and will affect service functionality. These URLs only correspond to Windows Virtual Desktop sites and resources, and don't include URLs for other services like Azure Active Directory.
100+
>
101+
>Windows Virtual Desktop now supports the FQDN tag.
99102
100103
The following table lists optional URLs that your Azure virtual machines can have access to:
101104

@@ -188,7 +191,9 @@ Available automation and deployment options depend on which OS and version you c
188191

189192
## Next steps
190193

191-
To get started, you'll need to create a tenant. To learn more about how to create a tenant, continue to the tenant creation tutorial.
194+
If you're using the Windows Virtual Desktop Fall 2019 release, you can get started with our tutorial at [Create a tenant in Windows Virtual Desktop](./virtual-desktop-fall-2019/tenant-setup-azure-active-directory.md).
195+
196+
If you're using the Windows Virtual Desktop Spring 2020 release, you'll need to create a host pool instead. Head to the following tutorial to get started.
192197

193198
> [!div class="nextstepaction"]
194-
> [Create a tenant in Windows Virtual Desktop](./virtual-desktop-fall-2019/tenant-setup-azure-active-directory.md)
199+
> [Create a host pool with the Azure portal](create-host-pools-azure-marketplace.md)

0 commit comments

Comments
 (0)