![]() For more information, see Use Azure Firewall to manage and secure Windows 365 environments. Windows 365 fully qualified domain name (FQDN) tags make it easier to grant access to Windows 365 required service endpoints through an Azure firewall. Use FQDN tags for endpoints through Azure Firewall GCCH: Required URLs for Azure Virtual Desktop for US government deployments.Ĭ.net:443Ĭ.net:443Ĭ.net:443Ĭ.net:443Ĭ.net:443Ĭ.net:443Ĭ.net:443Ĭ.net:443Īzure Active Directory-dependent URLs Address:PortĮ:443Īzure Virtual Device-dependent URLs Address:Port.GCCH: Microsoft Intune network endpoints for US government deployments.GCC: Azure Virtual Desktop required URL list.GCC: Network endpoints for Microsoft Intune.All endpoints connect over port 443 unless specified otherwise. You must allow traffic in your Azure network configuration to the service URLs and ports listed in this section. It performs core infrastructure functions such as domain join, initial config setup, data monitoring, and remediation. * The CMD Agent is required for the Windows 365 service. Provisioning and Azure network connection endpoints:.Azure Virtual Desktop required URL list.You must allow traffic in your Azure network configuration to the following service URLs and ports: For Government Community Cloud (GCC) and Government Community Cloud High (GCCH), this will be a US Gov region. Azure virtual network: You must have a virtual network (vNET) in your Azure Government subscription in the same region as where the Windows 365 Cloud PCs are created.The customer must have a subscription in the Azure Government environment.To use your own network and provision Azure AD joined Cloud PCs, you must meet the following requirements: The Azure vNet must have network access to an enterprise domain controller, either in Azure or on-premises.Īll of the Windows 365 Enterprise requirements apply to Windows 365 Government with the following additions: Azure Active Directory joined Cloud PCs.To support this resolution, define your AD DS DNS servers as the DNS servers for the virtual network. The Azure virtual network must be able to resolve DNS entries for your Active Directory Domain Services (AD DS) environment.To use your own network and provision Hybrid Azure AD joined Cloud PCs, you must meet the above requirements, and the following requirements: A subnet within the vNet and available IP address space.Network bandwidth: See Azure’s Network guidelines.Azure virtual network: You must have a virtual network (vNET) in your Azure subscription in the same region as where the Windows 365 desktops are created.To use your own network and provision Azure Active Directory (Azure AD) joined Cloud PCs, you must meet the following requirements:
0 Comments
Leave a Reply. |