From ec01ea06d83943d365de1521dab67678cf211423 Mon Sep 17 00:00:00 2001 From: ErikjeMS Date: Wed, 9 Oct 2024 11:45:47 -0700 Subject: [PATCH 1/5] uncenter table --- windows-365/enterprise/partner-integration-scenarios.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows-365/enterprise/partner-integration-scenarios.md b/windows-365/enterprise/partner-integration-scenarios.md index 3d3d20a5829..3a8078845c9 100644 --- a/windows-365/enterprise/partner-integration-scenarios.md +++ b/windows-365/enterprise/partner-integration-scenarios.md @@ -34,7 +34,7 @@ ms.collection: The following partner integration scenarios support partner protocols on top of Windows 365, without compromising the simplicity and predictability that Windows 365 delivers. | Partner | Supported clients | Gateway service | Connection protocol | -| :---: | :---: | :---: | :---: | +| --- | --- | --- | --- | | Citrix | Citrix Workspace web client
Citrix Workspace desktop clients for supported platforms | Citrix Cloud Gateway Service | Citrix HDX | | HP | HP Anyware web client
HP Anyware desktop clients for supported platforms | HP Anyware Cloud Gateway Service | HP Anyware | | Omnissa | Omnissa Workspace ONE web client
Omnissa ONE desktop clients for supported platforms | Omnissa Cloud Gateway Service | Omnissa Blast | From 3d46f7ba2877cfd7a6d2d6eabadf2edd3f293549 Mon Sep 17 00:00:00 2001 From: ErikjeMS Date: Wed, 9 Oct 2024 11:46:53 -0700 Subject: [PATCH 2/5] change --- windows-365/enterprise/partner-integration-scenarios.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows-365/enterprise/partner-integration-scenarios.md b/windows-365/enterprise/partner-integration-scenarios.md index 3a8078845c9..04c8f71bcb3 100644 --- a/windows-365/enterprise/partner-integration-scenarios.md +++ b/windows-365/enterprise/partner-integration-scenarios.md @@ -52,7 +52,7 @@ While scenarios not listed here might still work in customers’ production envi 1. A user authenticates using Microsoft Entra ID, on-premises Active Directory, or a third party identity provider. 2. Windows 365 establishes a connection to the partner cloud gateway using partner protocols. 3. A Cloud PC is assigned to the user and is accessible from the web/workspace portals. -4. Windows 365 establishes a connection to the Cloud PC using partner protocols. +4. Windows 365 establishes a connection to the Cloud PC using partner protocols. ## Next steps From f597589bd7a6d2ded4690b21e1bb641a2bbae166 Mon Sep 17 00:00:00 2001 From: "JerryAbo [MSFT]" <94194023+jerryabo@users.noreply.github.com> Date: Fri, 11 Oct 2024 11:21:50 -0500 Subject: [PATCH 3/5] Update azure-virtual-desktop-multi-session.md Needs PM review and verification. Filed based on investigations from 2 customer incidents, in which clean-up rules are not honored. Need to verify ok to link to blog, as that's only thing that mentions soft delete. If not wanting to mention soft delete, can just change to deleted automatically after 30 days and link to https://learn.microsoft.com/en-us/mem/intune/remote-actions/devices-wipe#automatically-delete-devices-with-cleanup-rules, which is linked off of blog. --- .../intune/fundamentals/azure-virtual-desktop-multi-session.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/memdocs/intune/fundamentals/azure-virtual-desktop-multi-session.md b/memdocs/intune/fundamentals/azure-virtual-desktop-multi-session.md index 9c207d54018..9c5bc23c4fe 100644 --- a/memdocs/intune/fundamentals/azure-virtual-desktop-multi-session.md +++ b/memdocs/intune/fundamentals/azure-virtual-desktop-multi-session.md @@ -223,7 +223,7 @@ The following Windows 10 or Windows 11 desktop device remote actions aren't supp ## Retirement -Deleting VMs from Azure will leave orphaned device records in the Microsoft Intune admin center. They'll be automatically cleaned up according to the cleanup rules configured for the tenant. +Deleting VMs from Azure will leave orphaned device records in the Microsoft Intune admin center. AVD machines will be soft deleted after 30 days of inacitivty and removed permanently after 60 days. For more information, see [Using Intune device cleanup rules](https://techcommunity.microsoft.com/t5/device-management-in-microsoft/using-intune-device-cleanup-rules-updated-version/ba-p/3760854). ## Security baselines From 869ad3f27dafdbf89a7e2318ea30cf78a78de4dd Mon Sep 17 00:00:00 2001 From: Doug Eby <17034284+dougeby@users.noreply.github.com> Date: Fri, 11 Oct 2024 10:53:27 -0700 Subject: [PATCH 4/5] Revert "Update azure-virtual-desktop-multi-session.md" --- .../intune/fundamentals/azure-virtual-desktop-multi-session.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/memdocs/intune/fundamentals/azure-virtual-desktop-multi-session.md b/memdocs/intune/fundamentals/azure-virtual-desktop-multi-session.md index 9c5bc23c4fe..9c207d54018 100644 --- a/memdocs/intune/fundamentals/azure-virtual-desktop-multi-session.md +++ b/memdocs/intune/fundamentals/azure-virtual-desktop-multi-session.md @@ -223,7 +223,7 @@ The following Windows 10 or Windows 11 desktop device remote actions aren't supp ## Retirement -Deleting VMs from Azure will leave orphaned device records in the Microsoft Intune admin center. AVD machines will be soft deleted after 30 days of inacitivty and removed permanently after 60 days. For more information, see [Using Intune device cleanup rules](https://techcommunity.microsoft.com/t5/device-management-in-microsoft/using-intune-device-cleanup-rules-updated-version/ba-p/3760854). +Deleting VMs from Azure will leave orphaned device records in the Microsoft Intune admin center. They'll be automatically cleaned up according to the cleanup rules configured for the tenant. ## Security baselines From 253e5c2931d83ef353268aa6582930d665fdb5f0 Mon Sep 17 00:00:00 2001 From: ErikjeMS Date: Fri, 11 Oct 2024 11:30:37 -0700 Subject: [PATCH 5/5] 54374136 provisioning errors --- windows-365/enterprise/provisioning-errors.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/windows-365/enterprise/provisioning-errors.md b/windows-365/enterprise/provisioning-errors.md index 954ece6646d..cdd3421b403 100644 --- a/windows-365/enterprise/provisioning-errors.md +++ b/windows-365/enterprise/provisioning-errors.md @@ -184,6 +184,10 @@ If you are seeing this error, some factors to consider are: - If the device is Intune-enrolled, you can apply Intune policy to disable the ports. - The user can also disable the ports manually by adding a local firewall rule onto their device. For a list of high risk ports that are recommended for blocking, please see [Security admin rules in Azure Virtual Network Manager](/azure/virtual-network-manager/concept-security-admins#protect-high-risk-ports). +## Other provisioning failures + +If you encounter other provisioning errors not covered above, make sure all the required endpoints are allowed on the VNet used for your ANC and any gateway device. + ## Next steps [Troubleshooting](troubleshooting.md).