You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: windows-365/enterprise/troubleshoot-azure-network-connection.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ When a Cloud PC is provisioned, it’s automatically joined to the provided doma
38
38
39
39
- The domain join user has sufficient permissions to join the domain provided.
40
40
- The domain join user can write to the organizational unit (OU) provided.
41
-
- The domain join user is not restricted in how many computers they can join. For example, the default maximum joins per user is 10 and this can affect Cloud PC provisioning.
41
+
- The domain join user isn't restricted in how many computers they can join. For example, the default maximum joins per user is 10 and this maximum can affect Cloud PC provisioning.
42
42
- The subnet being used can reach a domain controller.
43
43
- You test Add-Computer using the domain join credentials on a VM connected to the Cloud PC vNet/subnet.
44
44
- You troubleshoot domain join failures like any physical computer in your organization.
@@ -61,7 +61,7 @@ If provisioning fails, make sure that:
61
61
62
62
As part of the ANC setup, you provide a subnet. This subnet is used for all Cloud PCs during the provisioning process. Each Cloud PC provisioning will create a virtual NIC and consume an IP address from the subnet.
63
63
64
-
Make sure that there is sufficient IP Address allocation available for the volume of Cloud PCs you expect to provision. Also, plan enough address space for provisioning failures and potential disaster recovery.
64
+
Make sure that there's sufficient IP Address allocation available for the volume of Cloud PCs you expect to provision. Also, plan enough address space for provisioning failures and potential disaster recovery.
65
65
66
66
If this check fails, make sure that:
67
67
@@ -108,21 +108,21 @@ If this test fails, make sure that:
108
108
109
109
- You use the Azure Virtual Network troubleshooting tools to ensure that the provided vNet/subnet can reach the service endpoints listed in the doc.
110
110
- The DNS server provided can resolve the external services correctly.
111
-
- There is no proxy between the Cloud PC subnet and the internet.
111
+
- There's no proxy between the Cloud PC subnet and the internet.
112
112
- There are no firewall rules (physical, virtual, or in Windows) that might block required traffic.
113
113
- You consider testing the endpoints from a VM on the same subnet declared for Cloud PCs.
114
114
115
115
## Environment and configuration is ready
116
116
117
-
This check is used for many infrastructure related issues that might be related to infrastructure that customers are responsible for. It can include errors such as internal service time outs or those caused by customers deleting/changing Azure resources while checks are being run.
117
+
This check is used for many infrastructure related issues that might be related to infrastructure that customers are responsible for. It can include errors such as internal service time outs or errors caused by customers deleting/changing Azure resources while checks are being run.
118
118
119
119
Sometimes, these service errors are intermittent and a retry will complete successfully. Other times there’s no further troubleshooting that can be performed without the help of support.
120
120
121
-
We suggest you retry the checks in case of this error. If it persists, contact support for help.
121
+
We suggest you retry the checks if you encounter this error. If it persists, contact support for help.
122
122
123
123
## First party app permissions
124
124
125
-
When creating an ANC, the wizard grants a certain level of permissions on the resource group and subscription. This lets the service smoothly provision Cloud PCs.
125
+
When creating an ANC, the wizard grants a certain level of permissions on the resource group and subscription. These permissions let the service smoothly provision Cloud PCs.
126
126
127
127
These permissions can be viewed and modified by Azure admins who hold such permissions.
128
128
@@ -134,7 +134,7 @@ If any of these permissions are revoked, this check will fail. Make sure that th
134
134
135
135
The role assignment on the subscription will be granted to the Cloud PC service principal.
136
136
137
-
Also, make sure that the permissions haven't been granted as [classic subscription administrator roles](/azure/role-based-access-control/rbac-and-directory-admin-roles#classic-subscription-administrator-roles) or "Roles (Classic)". This role is not sufficient. It must be one of Azure role-based access control built-in roles as listed above.
137
+
Also, make sure that the permissions haven't been granted as [classic subscription administrator roles](/azure/role-based-access-control/rbac-and-directory-admin-roles#classic-subscription-administrator-roles) or "Roles (Classic)". This role isn't sufficient. It must be one of the Azure role-based access control built-in roles as listed above.
Copy file name to clipboardExpand all lines: windows-365/enterprise/troubleshooting.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,13 +40,13 @@ Since Cloud PCs work like most physical devices, you can use existing troublesho
40
40
41
41
## Audio and video redirection not working
42
42
43
-
For connections using the Remote Desktop client for Windows to access Cloud PCs, the first time a user logs on to their Cloud PC, Microsoft Teams will be installed.
43
+
For connections using the Remote Desktop client for Windows to access Cloud PCs, the first time a user signs in to their Cloud PC, Microsoft Teams will be installed.
44
44
45
45
After the installation, the optimizations to redirect audio and video to your local Windows endpoint don’t work. The user must close Teams and sign out from or restart the Cloud PC to activate the Optimized status.
46
46
47
47
## Conditional access
48
48
49
-
Make sure that you apply conditional access policies to the both dedicated Windows 365 cloud app and the Azure Virtual Desktop cloud app. You can apply these policies in the conditional access UI of Microsoft Endpoint Manager admin center or Azure Active Directory.
49
+
Make sure that you apply conditional access policies to both the dedicated Windows 365 cloud app and the Azure Virtual Desktop cloud app. You can apply these policies in the conditional access UI of Microsoft Endpoint Manager admin center or Azure Active Directory.
50
50
51
51
Any conditional access policy that you apply will affect:
52
52
@@ -57,7 +57,7 @@ For more information about service dependencies in Azure AD Conditional Access,
57
57
58
58
Applying a more restrictive policy to Azure Virtual Desktop than the Windows 365 cloud app will result in Azure AD honoring the more restrictive policy. This policy will affect end user connectivity to their Cloud PCs after accessing the Windows 365 end user portal.
59
59
60
-
For more information on how a given policy may impact your environment, see [Troubleshoot using the What If tool in Conditional Access](/azure/active-directory/conditional-access/what-if-tool).
60
+
For more information on how a given policy may affect your environment, see [Troubleshoot using the What If tool in Conditional Access](/azure/active-directory/conditional-access/what-if-tool).
61
61
62
62
## Help users in your organization
63
63
@@ -70,7 +70,7 @@ You can use the Intune Troubleshooting page to view enrollment issues, remediati
70
70
You can try either of these possible solutions:
71
71
72
72
- If the language pack installation failed, try reprovisioning the Cloud PC to install the language pack again.
73
-
- Check to see if there is an Attack Surface Reduction rule set on Intune. If the **Block process creations originating from PSExec and WMI commands** is set to Block, it will block language pack installation. You can remove the rule and retry provisioning, or provisioning with default language set to en-us. Then, let the user change the language by using the Windows Settings App in the Cloud PC.
73
+
- Check to see if there's an Attack Surface Reduction rule set on Intune. If the **Block process creations originating from PSExec and WMI commands** is set to Block, it will block language pack installation. You can remove the rule and retry provisioning, or provisioning with default language set to en-us. Then, let the user change the language by using the Windows Settings App in the Cloud PC.
Copy file name to clipboardExpand all lines: windows-365/enterprise/whats-new.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,7 +56,7 @@ Learn what new features are available in Windows 365 Enterprise.
56
56
57
57
#### Cloud PC Outlook mail sync setting<!--40423390-->
58
58
59
-
For newly provisioned and reprosivioned Cloud PCs, you can now set the Outlook mail sync setting to 6 or 12 months.
59
+
For newly provisioned and reprovisioned Cloud PCs, you can now set the Outlook mail sync setting to 6 or 12 months.
60
60
61
61
<!-- vvvvvvvvvvvvvvvvvvvvvv -->
62
62
### Device management
@@ -205,7 +205,7 @@ The [windows365.microsoft.com](https://windows365.microsoft.com/) web client has
205
205
206
206
#### Upload a custom image without an Azure network connection<!--8341750 -->
207
207
208
-
Customers using Azure Active Directory (Azure AD) Join without bringing an Azure virtual network can now upload custom images directly on the image tab in Microsoft Endpoint Manager. Previously, to upload an image, customers needed to create an ANC for the destination Azure subscription which provides the image.
208
+
Customers using Azure Active Directory (Azure AD) Join without bringing an Azure virtual network can now upload custom images directly on the image tab in Microsoft Endpoint Manager. Previously, to upload an image, customers needed to create an ANC for the destination Azure subscription that provides the image.
209
209
210
210
#### Cloud PC name appended to the network interface name<!--38793957-->
211
211
@@ -325,7 +325,7 @@ We've added information to the help documentation about the update cycle for Win
325
325
326
326
#### Cloud PCs in grace period count towards active Cloud PC license usage<!-- 37017463-->
327
327
328
-
Cloud PCs that are in grace period now count towards your active Cloud PC license usage. This makes sure that your organization’s active Cloud PC allocation matches the total available licenses in your tenant.
328
+
Cloud PCs that are in grace period now count towards your active Cloud PC license usage. This policy makes sure that your organization’s active Cloud PC allocation matches the total available licenses in your tenant.
329
329
330
330
For more information about grace period, see [Device management overview](device-management-overview.md) and [End grace period](end-grace-period.md).
331
331
@@ -395,7 +395,7 @@ Custom Windows 365 role-based access control (RBAC) roles are now available in t
395
395
396
396
#### Resize support for preview and trial licenses<!--36228235-->
397
397
398
-
If you have a combination of paid and free trial licenses, the Resize remote action will use your paid licenses first. When those run out, it will use your trial licenses. For more information, see [Resize a Cloud PC](resize-cloud-pc.md).
398
+
If you have a combination of paid and free trial licenses, the Resize remote action will use your paid licenses first. When those licenses run out, it will use your trial licenses. For more information, see [Resize a Cloud PC](resize-cloud-pc.md).
0 commit comments