Merge pull request #16490 from MicrosoftDocs/main

Publish main to live, Wednesday 10:30 AM PST, 10/30

Author: padmagit77

windows-365/enterprise/azure-network-connections.md

@@ -7,7 +7,7 @@ keywords:
 author: ErikjeMS  
 ms.author: erikje
 manager: dougeby
-ms.date: 08/28/2024
+ms.date: 10/30/2024
 ms.topic: overview
 ms.service: windows-365
 ms.subservice: windows-365-enterprise
@@ -47,8 +47,8 @@ There are two kinds of ANCs based on their join type. Both let you manage traffi
 
 When a Cloud PC is provisioned, the information in the ANC is used by the provisioning policy to provision the Cloud PC in the Azure subnet. The information required in an ANC includes:
 
-- **Network details**: The Azure subscription, resource group, virtual network, and subnet that the Cloud PC will be associated with. When a provisioning policy runs, it creates a Cloud PC in the Microsoft hosted Azure subscription. To connect to a customer's on-premises network, a virtual network interface card (vNic) is injected into a customer-provided Azure virtual network (vNet). To create this vNic, Windows 365 needs sufficient access to an Azure subscription.
-- **Active Directory domain**: The Active Directory domain to join, an Organizational Unit (OU) destination for the computer object, and Active Directory user credentials with sufficient permissions to perform the domain join. When a provisioning policy runs, the Cloud PC is joined to this Active Directory domain. The credentials will be stored securely in the Windows 365 service.
+- **Network details**: The Azure subscription, resource group, virtual network, and subnet to associate with the Cloud PC. When a provisioning policy runs, it creates a Cloud PC in the Microsoft hosted Azure subscription. To connect to a customer's on-premises network, a virtual network interface card (vNic) is injected into a customer-provided Azure virtual network (vNet). To create this vNic, Windows 365 needs sufficient access to an Azure subscription.
+- **Active Directory domain**: The Active Directory domain to join, an Organizational Unit (OU) destination for the computer object, and Active Directory user credentials with sufficient permissions to perform the domain join. When a provisioning policy runs, the Cloud PC is joined to this Active Directory domain. The credentials are stored securely in the Windows 365 service.
 
 During provisioning, the Cloud PC is connected to the Azure subnet and joined to a domain (either Windows Server Active Directory or Microsoft Entra ID). This process results in a Cloud PC that is:
 
@@ -61,7 +61,7 @@ The ANC settings are applied to the Cloud PC only at the time of provisioning.
 
 ### Alternate ANCs
 
-To help make provisioning Cloud PCs more reliable in the rare case of capacity constraints in a region, you have the option to assign alternate ANCs to a provisioning policy. You can define the priority order of the ANCs that the policy will use. If the first ANC is unavailable, the policy will automatically use the second ANC in the priority list. If the second one is unavailable, it will move on to the next, and so on. This lets administrators prepare multiple ANCs in different Azure regions, making provisioning more reliable. You don't have to use multiple ANCs. For more information about using alternate ANCs when creating your provisioning policies, see [Create provisioning policies](create-provisioning-policy.md).
+To help make provisioning Cloud PCs more reliable in the rare case of capacity constraints in a region, you can assign alternate ANCs to a provisioning policy. You can define the priority order of the ANCs that the policy uses. If the first ANC is unavailable, the policy automatically uses the second ANC in the priority list. If the second one is unavailable, it moves on to the next, and so on. This process lets administrators prepare multiple ANCs in different Azure regions, making provisioning more reliable. You don't have to use multiple ANCs. For more information about using alternate ANCs when creating your provisioning policies, see [Create provisioning policies](create-provisioning-policy.md).
 
 ## First health check
 
@@ -81,7 +81,7 @@ After provisioning, the information in an ANC is also used to monitor:
 - the connection health between your network-based resources
 - the Cloud PC hosted in the Microsoft hosted subscription
 
-Windows 365 will report configuration issues that may cause provisioning failures or poor end-user experiences. This monitoring reduces your management overhead. For more information on these periodic checks, see [Azure network connection health checks](health-checks.md).
+Windows 365 reports configuration issues that may cause provisioning failures or poor end-user experiences. This monitoring reduces your management overhead. For more information on these periodic checks, see [Azure network connection health checks](health-checks.md).
 
 ## Health check frequency
 
@@ -102,13 +102,13 @@ The ANC wizard requires access to Azure and, optionally, on-premises domain reso
 - [Intune Administrator](/azure/active-directory/roles/permissions-reference#intune-administrator) or [Windows 365 Administrator](/azure/active-directory/roles/permissions-reference) role.
 - An Active Directory user account with sufficient permissions to join the AD domain into this Organizational Unit (Microsoft Entra hybrid join ANCs only).
 
-To create or edit an ANC, you must at least have the Subscription Reader role in the Azure Subscription where the VNET associated with the ANC was located.
+To create or edit an ANC, you must have at least the Subscription Reader role in the Azure Subscription where the VNET associated with the ANC was located.
 
 For a full list of requirements, see [Windows 365 requirements](requirements.md).
 
 ## Changing an Azure network connection
 
-Changing the settings in an ANC won’t affect Cloud PCs previously provisioned with that ANC. Only Cloud PCs provisioned after the changes to the ANC will reflect such later changes.
+Changing the settings in an ANC won’t affect Cloud PCs previously provisioned with that ANC. Only Cloud PCs provisioned after the changes to the ANC reflect such later changes.
 
 If you want to change the ANC related settings on a previously provisioned Cloud PC, you must reprovision the Cloud PC. Reprovisioning is a destructive action, so be sure it's an action you really want to take. For more information, see [reprovisioning](provisioning.md#reprovisioning).  
 
@@ -125,6 +125,10 @@ After completing either of these operations, you can delete the ANC.
 
 Each tenant has a limit of 10 Azure network connections. If your organization needs more than 10 Azure network connections, contact support.
 
+## Inactive ANCs
+
+ANCs that are unused for a period of time become inactive. Inactive ANCs pause running health checks and can't be assigned to a provisioning policy until the ANC is reactivated and health checks complete successfully.  
+
 ## User sign-in
 
 When users attempt to sign in to their Cloud PC, user authentication occurs.

windows-365/enterprise/create-azure-network-connection.md

@@ -7,7 +7,7 @@ keywords:
 author: ErikjeMS  
 ms.author: erikje
 manager: dougeby
-ms.date: 04/01/2024
+ms.date: 10/30/2024
 ms.topic: how-to
 ms.service: windows-365
 ms.subservice: windows-365-enterprise
@@ -68,7 +68,7 @@ When planning your ANC VNets with ExpressRoute as the on-premises connectivity m
 
     ![Screenshot of Name field](./media/create-azure-network-connection/connection-name.png)
 
-4. Select a **Subscription** and **Resource group** for the new connection. Create a new resource group to contain your Cloud PC resources. Optionally, you can instead select an existing resource group in the list (which grant Windows 365 permissions to the existing resource group). If you don’t have a [healthy ANC](health-checks.md), you won't be able to proceed.
+4. Select a **Subscription** and **Resource group** for the new connection. Create a new resource group to contain your Cloud PC resources. Optionally, you can instead select an existing resource group in the list (which grant Windows 365 permissions to the existing resource group). If you don’t have a [healthy ANC](health-checks.md), you can't proceed.
 5. Select a **Virtual network** and **Subnet**.
 6. Select **Next**.
 7. For hybrid Microsoft Entra join ANCs, on the **AD domain** page, provide the following information:
@@ -88,6 +88,8 @@ When planning your ANC VNets with ExpressRoute as the on-premises connectivity m
 8. Select **Next**.
 9. On the **Review + Create** page, select **Create**.
 
+When an ANC is in use, it can't be deleted and certain configuration settings can't be edited. For more information, see [Edit Azure network connection](edit-azure-network-connection.md) and [Delete Azure network connection](delete-azure-network-connection.md).
+
 <!-- ########################## -->
 ## Next steps
 

windows-365/enterprise/delete-azure-network-connection.md

@@ -7,7 +7,7 @@ keywords:
 author: ErikjeMS  
 ms.author: erikje
 manager: dougeby
-ms.date: 07/25/2024
+ms.date: 10/30/2024
 ms.topic: how-to
 ms.service: windows-365
 ms.subservice: windows-365-enterprise
@@ -31,18 +31,29 @@ ms.collection:
 
 # Delete Azure network connection
 
-Only an unassigned Azure network connection (ANC) can be deleted. If an ANC is in use by a provisioning policy, then you must take one of the following steps:
+Only an unused Azure network connection (ANC) can be deleted.
 
-- Remove the ANC from all provisioning policies.
-- Delete the ANC.
-
-To delete an Azure network connection:
+To delete an unused ANC:
 
 1. Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431) > **Devices** > **Windows 365** (under **Provisioning**) > **Azure network connection**. You must have [Intune Administrator](/azure/active-directory/roles/permissions-reference#intune-administrator) or [Windows 365 Administrator](/azure/active-directory/roles/permissions-reference) permissions.
 ![Screenshot of delete connection](./media/delete-azure-network-connection/delete-connection.png)
 2. Select the ellipses (**…**) next to the connection you want to delete > **Delete**.
 3. Select **Confirm** when asked to delete the connection.
 
+## In use ANCs
+
+ANCs that are in use can't be deleted. In use ANCs include ANCs that are:
+
+- Referenced by a provisioning policy, including as an alternate ANC.
+- Used by a Cloud PC.
+- Configured as backup ANCs for [cross region disaster recovery](cross-region-disaster-recovery.md).
+
+If an ANC is in use, then you must take one of the following steps before you can delete it:
+
+- Remove the ANC from all provisioning policies.
+- Move Cloud PCs to another ANC or deprovision the Cloud PCs.
+- Remove the ANC from all cross region disaster recovery user settings.
+
 <!-- ########################## -->
 ## Next steps
 

windows-365/enterprise/edit-azure-network-connection.md

@@ -7,7 +7,7 @@ keywords:
 author: ErikjeMS  
 ms.author: erikje
 manager: dougeby
-ms.date: 07/25/2024
+ms.date: 10/30/2024
 ms.topic: how-to
 ms.service: windows-365
 ms.subservice: windows-365-enterprise
@@ -44,10 +44,16 @@ To edit an Azure network connection:
 1. Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431) > **Devices** > **Windows 365** (under **Provisioning**) > **Azure network connection** > select the connection you want to edit > **Properties**.
 2. For all ANCs, you can edit the **General** settings by selecting **Edit** next to each header. You can edit all settings except **Join type**. For Microsoft Entra hybrid join connections, you can also edit the **AD domain** settings.
 
-After the edits have been saved, the ANC checks are run to verify the configuration.
+After the edits are saved, the ANC checks are run to verify the configuration.
 
 You can't edit an ANC if it's running checks. You must wait for the checks to pass/fail before edit functionality becomes available.
 
+Some configuration settings can't be edited for ANCs that are:
+
+- Referenced by a provisioning policy, including as an alternate ANC.
+- Used by a Cloud PC.
+- Configured as backup ANCs for [cross region disaster recovery](cross-region-disaster-recovery.md).
+
 <!-- ########################## -->
 ## Next steps
 

windows-365/enterprise/health-checks.md

@@ -7,7 +7,7 @@ keywords:
 author: ErikjeMS
 ms.author: erikje
 manager: dougeby
-ms.date: 08/28/2024
+ms.date: 10/30/2024
 ms.topic: how-to
 ms.service: windows-365
 ms.subservice: windows-365-enterprise
@@ -44,12 +44,13 @@ Statuses include:
 
 - **Running checks**: The health checks are currently running. The ANC list view automatically refreshes every five minutes. Wait for the checks to complete before attempting to assign it to a provisioning policy.
 - **Checks successful**: All health checks passed. The ANC is ready for use.
-- **Checks successful with warnings**: All critical health checks passed. However at least one non-critical check may have issues. An example of a check that may trigger this state is the Microsoft Entra hybrid join sync check. Microsoft Entra hybrid join sync can take up to 90 minutes, so we check much of the Microsoft Entra hybrid join sync service but can’t confirm the device sync succeeded until later. ANCs with this status can be used by provisioning policies.
-- **Checks failed**: One or more required checks failed. An ANC can’t be used if it's in a failed state. You’ll have to resolve the underlying issue and Retry the health checks.
+- **Checks successful with warnings**: All critical health checks passed. However at least one noncritical check may have issues. An example of a check that may trigger this state is the Microsoft Entra hybrid join sync check. Microsoft Entra hybrid join sync can take up to 90 minutes. Therefore, we check much of the Microsoft Entra hybrid join sync service but can’t confirm that the device sync succeeded until later. Provisioning policies can use ANCs with this status.
+- **Checks failed**: One or more required checks failed. An ANC can’t be used if it's in a failed state. Resolve the underlying issue and Retry the health checks.
+- **Inactive**: The ANC is inactive and health checks are paused. Reactivate the ANC to restart the health checks. After the health checks are passed, the ANC is ready for use.
 
 ## Status error details
 
-Every failed ANC or success with warning error state includes the technical details behind the failure. Select the **View details** link for each failed check to view more information on the failure. After you’ve fixed the underlying issue, **Retry** the health check to rerun the tests. To retry the health check, you must:
+Every failed ANC or success with warning error state includes the technical details behind the failure. Select the **View details** link for each failed check to view more information on the failure. After you fix the underlying issue, **Retry** the health check to rerun the tests. To retry the health check, you must:
 
 - Have the [Intune Administrator](/azure/active-directory/roles/permissions-reference#intune-administrator) or [Windows 365 Administrator](/azure/active-directory/roles/permissions-reference) role.
 

windows-365/enterprise/report-cloud-pc-actions.md

@@ -7,7 +7,7 @@ keywords:
 author: ErikjeMS  
 ms.author: erikje
 manager: dougeby
-ms.date: 12/6/2023
+ms.date: 10/30/2024
 ms.topic: overview
 ms.service: windows-365
 ms.subservice: windows-365-enterprise
@@ -31,19 +31,24 @@ ms.collection:
 
 # Cloud PC actions report (preview)
 
-This report shows you what actions admins have taken on which Cloud PCs, and the status of those actions.
+This report shows you the status and completion progress of actions admins have taken on Cloud PCs, for both:
+
+- Single actions on the **Devices** tab.
+- Multiple devices using **Bulk device actions** on the **Bulk batches** tab.
+
+ The report shows action statuses for the last 90 days.
 
 The Cloud PC actions report is in [public preview](..\public-preview.md).
 
 ## Use the Cloud PC actions report
 
 To get to the **Cloud PC actions** report, sign in to [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431), select **Devices** > **Monitor** > **Cloud PC actions (preview)**.
 
-## Report data
+## Devices tab
 
 :::image type="content" source="./media/report-cloud-pc-actions/report.png" alt-text="Screenshot of the Cloud PC actions report." lightbox="./media/report-cloud-pc-actions/report.png":::
 
-The report shows the following columns:
+The tab shows the following columns:
 
 - **Device name**
 - **Primary user UPN**
@@ -64,6 +69,17 @@ The report shows the following columns:
   - **Review required**: An admin must take action to complete the action. For example, assigning a target license to a device in **Resize Pending License** state for the **Resize** action.
 - **Date initiated**
 
+## Bulk batches tab
+
+When an admin takes an action on multiple Cloud PCs at once using **Bulk device actions**, the actions are combined into a batch.
+
+The tab shows the following columns:
+
+- **Batch name** - An automatically generated name for a batch of devices undergoing a remote action.
+- **Action** - Same as **Devices** tab.
+- **Completion** - The progress of the action on the batch of devices.
+- **Date initiated**
+
 <!-- ########################## -->
 ## Next steps
 

windows-365/enterprise/whats-new.md

@@ -55,6 +55,32 @@ For more information about public preview items, see [Public preview in Windows
 ### Windows 365 app 
 -->
 
+<!-- ########################## -->
+## Week of October 28, 2024 (Service release 2410)
+
+<!-- vvvvvvvvvvvvvvvvvvvvvv -->
+### Device management
+
+#### Bulk Troubleshoot action now generally available<!--51893512-->
+
+The Troubleshoot action in bulk has moved out of preview and into general availability.
+
+For more information, see [Remotely manage Windows 365 devices](remotely-manage-cloud-pc.md).
+
+<!-- vvvvvvvvvvvvvvvvvvvvvv -->
+### Monitor and troubleshoot
+
+### Update to Cloud PC action status report<!--49451077-->
+
+The Cloud PC action status report now shows batches of devices on which actions were triggered. You can see the batch current progress. For more information, see [Cloud PC actions report ](report-cloud-pc-actions.md).
+
+### Azure network connections inactive state<!--52127015-->
+
+Azure network connections that meet either of the following conditions for more than four weeks are now marked as inactive:
+
+- ANCs that aren't associated with provisioning policies.
+- ANCs with provisioning policies that have no Cloud PCs associate with them.
+
 <!-- ########################## -->
 ## Week of October 21, 2024
 
@@ -75,8 +101,6 @@ You can now use Citrix HDX Plus with Windows 365 Frontline Cloud PCs.
 
 Core TCP-based RDP traffic for Cloud PC connections uses the *.wvd.microsoft.com wildcard fully qualified domain name (FQDN). The FQDN remains unchanged, but the underlying IP addresses associated with it will shortly be changed to a single subnet. This will simplify optimization of this traffic and reduce the need for future change management.
 
-For more information, see [Plan for change: New Windows 365 IP Subnet for RDP Connectivity](https://iridias.microsoft.com/messagecenter?id=894574) Message Center post.
-
 <!-- vvvvvvvvvvvvvvvvvvvvvv -->
 ### Device management