Skip to content

Commit e6bbd42

Browse files
committed
more acrolinx fixes
1 parent b1e9838 commit e6bbd42

9 files changed

Lines changed: 19 additions & 19 deletions

windows-365/business-enterprise-comparison.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ Windows 365 is available in two editions: [Windows 365 Business](./business/inde
6767
| Capability | Windows 365 Business | Windows 365 Enterprise |
6868
| --- | --- | --- |
6969
| Management | Users can [restart, reset, rename, and troubleshoot](./end-user-access-cloud-pc.md#user-actions) their Cloud PCs on the Windows 365 homepage. | Users can [restart, rename, and troubleshoot](end-user-access-cloud-pc.md) their Cloud PCs on the Windows 365 homepage. |
70-
| Role | By default, each user is a Standard User on their Cloud PC. To grant Local Administrator permissions to a specific user on a Cloud PC, see [Remote management actions](./business/remotely-manage-business-cloud-pcs.md#remote-management-actions). To grant Local Administrator permissions for Cloud PCs that you create in the future, see [Change organizational default settings](./business/change-organization-default-settings.md).| By default, each user is assigned a standard user role on their Cloud PC. This can be changed by the admin in the Microsoft Endpoint Manager admin center.|
70+
| Role | By default, each user is a Standard User on their Cloud PC. To grant Local Administrator permissions to a specific user on a Cloud PC, see [Remote management actions](./business/remotely-manage-business-cloud-pcs.md#remote-management-actions). To grant Local Administrator permissions for Cloud PCs that you create in the future, see [Change organizational default settings](./business/change-organization-default-settings.md).| By default, each user is assigned a standard user role on their Cloud PC. This role can be changed by the admin in the Microsoft Endpoint Manager admin center.|
7171
| Access | Users can access their Cloud PC at windows365.microsoft.com or by using Microsoft Remote Desktop. | Users can access their Cloud PC at windows365.microsoft.com or by using Microsoft Remote Desktop. |
7272
| Platform | Any platform that supports Microsoft Remote Desktop clients. [Learn more.](/windows-server/remote/remote-desktop-services/clients/remote-desktop-clients) | Any platform that supports Microsoft Remote Desktop clients. [Learn more.](/windows-server/remote/remote-desktop-services/clients/remote-desktop-clients) |
7373

windows-365/business/troubleshoot-windows-365-business.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ Make sure **Users may join devices to Azure AD** is set to **All**.
4545
4. If **Users may join devices to Azure AD** isn't set to **All**, select **All**, then select **Save**.
4646
5. Go to [Step 2. Verify that the Windows 365 BPRT Permanent User system account is active](#step-2-verify-that-the-windows-365-bprt-permanent-user-system-account-is-active).
4747

48-
Make sure that **Maximum number of devices per user** is high enough so that the Cloud PCs you are trying to setup can be assigned to the designated users.
48+
Make sure that **Maximum number of devices per user** is high enough so that the Cloud PCs you're trying to setup can be assigned to the designated users.
4949

5050
1. Sign in to the Microsoft Azure portal at [https://portal.azure.com/](https://portal.azure.com/).
5151
2. Under **Manage Azure Active Directory**, select **View**.
@@ -57,15 +57,15 @@ Make sure that **Maximum number of devices per user** is high enough so that the
5757

5858
The first time a Windows 365 license is assigned in your organization, a system account called **Windows 365 BPRT Permanent User** is automatically created in Azure AD.
5959

60-
Do not delete this account or make any changes to it (such as changing the name or UPN). If the system account is modified or deleted, the setup will fail. This system account ensures a smooth setup process and doesn't have any write capabilities or access to your organization beyond the scoped service capabilities of Windows 365 Business. If you delete or modify this system account you must login to windows365.microsoft.com with any account that has a Windows 365 Business license and wait 12 hours for the token to refresh.
60+
Don't delete this account or make any changes to it (such as changing the name or UPN). If the system account is modified or deleted, the setup will fail. This system account ensures a smooth setup process and doesn't have any write capabilities or access to your organization beyond the scoped service capabilities of Windows 365 Business. If you delete or modify this system account, you must sign in to windows365.microsoft.com with any account that has a Windows 365 Business license and wait 12 hours for the token to refresh.
6161

6262
To make sure the Windows 365 BPRT Permanent User system account is active in Azure AD, use the following steps.
6363

6464
1. In the Azure portal, go to the [Azure Active Directory Overview](https://go.microsoft.com/fwlink/p/?linkid=516942) page.
6565
2. In the left nav, under **Manage**, select **Users**.
6666
3. In the search box, type **Windows 365 BPRT Permanent User**, then press **Enter**.
6767
4. If the Windows 365 BPRT Permanent User system account is present, go to [Step 3. Verify that device-based MFA is turned off](#step-3-verify-that-device-based-mfa-is-turned-off).
68-
5. If the Windows 365 BPRT Permanent User system account is missing or if any changes were made to it (for example, password reset, property change, assign or un-assign a license, and so on), please login to windows365.microsoft.com with any account that has a Windows 365 Business license assigned after 12 hours. A new Windows 365 BPRT Permanent User will be generated. After the token has regenerated, go directly to [Step 6. Reset your Cloud PCs](#step-6-reset-your-cloud-pcs).
68+
5. If the Windows 365 BPRT Permanent User system account is missing or if any changes were made to it (for example, password reset, property change, assign or unassign a license, and so on), sign in to windows365.microsoft.com with any account that has a Windows 365 Business license assigned after 12 hours. A new Windows 365 BPRT Permanent User will be generated. After the token has regenerated, go directly to [Step 6. Reset your Cloud PCs](#step-6-reset-your-cloud-pcs).
6969

7070
## Step 3. Verify that device-based MFA is turned off
7171

@@ -113,7 +113,7 @@ If you already use Microsoft Intune, or plan to use it to manage your Windows 36
113113
3. On the **Configure** page, next to **MDM user scope**, select **Some** or **All**, then select **Save**.
114114
4. In the left nav, under **Manage**, select **Mobility (MDM and MAM)**, select **Microsoft Intune Enrollment**, then repeat step 3.
115115

116-
Users who are assigned a Cloud PC must have an Intune license assigned to them. The CloudPCBPRT system account does not need to be assigned an Intune license.
116+
Users who are assigned a Cloud PC must have an Intune license assigned to them. The CloudPCBPRT system account doesn't need to be assigned an Intune license.
117117

118118
> [!IMPORTANT]
119119
> To assign licenses, you must be a Global or Licensing admin, or have a role with licensing permissions.
@@ -136,15 +136,15 @@ If you don’t plan to use Microsoft Intune for your Cloud PC management, you mu
136136

137137
1. In the Azure portal, go to the [Azure Active Directory Overview](https://go.microsoft.com/fwlink/p/?linkid=516942) page.
138138
2. In the left nav, under **Manage**, select **Mobility (MDM and MAM)**, then select **Microsoft Intune**.
139-
3. On the **Configure** page, you will see one of two things. If you have an Azure AD Premium subscription, select **None** next to MDM user scope, then select **Save**. If you do not have an Azure AD Premium subscription, select **Disable**.
139+
3. On the **Configure** page, you'll see one of two things. If you have an Azure AD Premium subscription, select **None** next to MDM user scope, then select **Save**. If you don't have an Azure AD Premium subscription, select **Disable**.
140140
4. In the left nav, under **Manage**, select **Mobility (MDM and MAM)**, select **Microsoft Intune Enrollment**, then repeat step 3.
141141
5. Go to [Step 6. Reset your Cloud PCs](#step-6-reset-your-cloud-pcs).
142142

143143
## Step 6. Reset your Cloud PCs
144144

145145
After you complete the troubleshooting steps in this article, your users must restart their Cloud PC setup.
146146

147-
If you just completed [Step 3. Verify that device-based MFA is turned off](#step-3-verify-that-device-based-mfa-is-turned-off), wait at least ten minutes for the changes to take effect before you continue. Make sure that the user you excluded from MFA is the first users to sign in to the [Windows 365 home page](https://windows365.microsoft.com).
147+
If you just completed [Step 3. Verify that device-based MFA is turned off](#step-3-verify-that-device-based-mfa-is-turned-off), wait at least 10 minutes for the changes to take effect before you continue. Make sure that the user you excluded from MFA is the first users to sign in to the [Windows 365 home page](https://windows365.microsoft.com).
148148

149149
Tell all Cloud PC users who saw the “Setup failed” error to use the following steps to reset their Cloud PCs.
150150

windows-365/business/whats-new.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -114,7 +114,7 @@ Users can now restore a Cloud PC to a state from a previous point in time. Multi
114114

115115
#### Windows 365 link on Microsoft 365 admin center<!--37188422 -->
116116

117-
To make it easier for admins to set up Windows 365, a link has been added to the M365 admin center home page. Admins with Windows 365 Enterprise licenses will see a link for [endpoint.microsoft.com](https://endpoint.microsoft.com) and admins with Windows 365 Business licenses will see a link for [windows365.microsoft.com](https://windows365.microsoft.com).
117+
To make it easier for admins to set up Windows 365, a link has been added to the Microsoft 365 admin center home page. Admins with Windows 365 Enterprise licenses will see a link for [endpoint.microsoft.com](https://endpoint.microsoft.com) and admins with Windows 365 Business licenses will see a link for [windows365.microsoft.com](https://windows365.microsoft.com).
118118

119119
#### Higher Cloud PC screen resolution option (preview)<!--38301718 wnready-->
120120

windows-365/end-user-access-cloud-pc.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -90,7 +90,7 @@ While on windows365.microsoft.com, users can take actions on their Cloud PCs by
9090

9191
### Transfer files to and from a Cloud PC
9292

93-
To transfer files from the local device to the Cloud PC, click on the upload icon to launch File Explorer. Select the files to transfer them to the Uploads folder on the Cloud PC.
93+
To transfer files from the local device to the Cloud PC, select the upload icon to launch File Explorer. Select the files to transfer them to the Uploads folder on the Cloud PC.
9494

9595
To transfer files from the Cloud PC to the local device, copy the files to the Downloads folder on the Cloud PC. The files will be copied to the Downloads folder of the local device.
9696

windows-365/export-cloud-pc-names.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -63,9 +63,9 @@ Disconnect-MgGraph
6363
```
6464

6565
7. Save the file as “GetCloudPCNames.ps1” in a location of your choice.
66-
8. In the file explorer navigate to your file location.
67-
9. Right click on the file and select **Run with PowerShell**.
68-
10. A PowerShell window will pop up. In the window type “CloudPCNames.csv” and press enter.
69-
11. When the authentication Window pops up, log in with the same account you used to access the Cloud PC.
66+
8. In the file explorer, navigate to your file location.
67+
9. Right-click on the file and select **Run with PowerShell**.
68+
10. A PowerShell window will pop up. In the window, type “CloudPCNames.csv” and then press enter.
69+
11. When the authentication Window pops up, sign in with the same account you used to access the Cloud PC.
7070

71-
When the PowerShell window closes the script has finished running. Go back to the location of your script and there will be a file called “CloudPCNames.csv” which includes the list of all Cloud PC names on your tenant.
71+
When the PowerShell window closes, the script has finished running. Go back to the location of your script and there will be a file called “CloudPCNames.csv”. This file includes the list of all Cloud PC names on your tenant.

windows-365/includes/known-issues.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ For more information, see [Machine Account Password Process](https://techcommuni
2626

2727
## Cursor visible location offset from actual position
2828

29-
In a remote desktop session, when you click one position in a text file, the cursor in the Cloud PC has some offset with the real position.
29+
In a remote desktop session, when you select one position in a text file, the cursor in the Cloud PC has some offset with the real position.
3030

3131
**Possible cause**: In high DPI mode, both the server and Cloud PC browser scale the cursor. This conflict results in an offset between the visible cursor position and the actual cursor focus.
3232

@@ -42,4 +42,4 @@ Outlook only downloads one month of previous mail and this can't be changed in O
4242
2. Remove the **syncwindowsetting** regkey under the path \HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\office\16.0\outlook\cached mode.
4343
3. Add the **syncwindowsetting** regkey with the value 1 under the path HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Cached Mode.
4444

45-
After completing these steps, the default will be one month. However, the download period can be changed in Outlook settings.
45+
After you complete these steps, the default will be one month. However, the download period can be changed in Outlook settings.

windows-365/includes/outbound-data-rates.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,4 +9,4 @@ ms.author: erikje
99
ms.custom: include file
1010
---
1111

12-
Outbound data/month is based on the RAM of the Cloud PC:<br>- 2-GB RAM = 12-GB outbound data<br>- 4 or 8-GB RAM = 20-GB outbound data<br>- 16-GB RAM = 40-GB outbound data<br>- 32-GB RAM = 70-GB outbound data<br>Data bandwidth may be restricted when these levels are exceeded.
12+
Outbound data/month is based on the RAM of the Cloud PC:<br>- 2-GB RAM = 12-GB outbound data<br>- 4-GB or 8-GB RAM = 20-GB outbound data<br>- 16-GB RAM = 40-GB outbound data<br>- 32-GB RAM = 70-GB outbound data<br>Data bandwidth may be restricted when these levels are exceeded.

windows-365/includes/restore-risks-best-practices.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,4 +20,4 @@ Cloud PCs have same risks as all Windows PCs when performing a full disk restore
2020
## Best practices
2121

2222
- To minimize data loss and the risk of a rolling password conflict, choose a restore point that is as close as possible to the current time.
23-
- After a restoration is complete, the user should immediately sign into their Cloud PC to verify that they can successfully connect. If a user can't connect, or experiences unexpected behavior, try a second restoration to a different restore point that is more recent. On rare occasions you may need to reprovision/reset a Cloud PC if all restore points have obsolete rolling credentials.
23+
- After a restoration is complete, the user should immediately sign into their Cloud PC to verify that they can successfully connect. If a user can't connect, or experiences unexpected behavior, try a second restoration to a different restore point that is more recent. On rare occasions, you may need to reprovision/reset a Cloud PC if all restore points have obsolete rolling credentials.

windows-365/partners.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ ms.collection: M365-identity-device-management
3030

3131
# Windows 365 approved partners
3232

33-
Windows 365 gives opportunities to independent software vendors. When building their Windows apps, these partners can reach a broader audience by delivering their apps in the cloud.
33+
Windows 365 gives opportunities to independent software vendors. When partners build their Windows apps, they can reach a broader audience by delivering their apps in the cloud.
3434

3535
Here’s the list of approved partners that build and innovate with Windows 365.
3636

0 commit comments

Comments
 (0)