Opening these URLs is essential for a reliable client experience. Select the relevant tab based on which cloud you're using. Remote Desktop clientsĪny Remote Desktop clients you use to connect to Azure Virtual Desktop must have access to the URLs below. If you're using a Next Generation Firewall (NGFW), you'll need to use a dynamic list specifically made for Azure IPs to make sure you can connect. We only support unblocking specific URLs. ![]() For other services, see Available service tags.Īzure Virtual Desktop currently doesn't have a list of IP address ranges that you can unblock to allow network traffic. They don't include URLs for other services like Azure Active Directory. The listed URLs and tags only correspond to Azure Virtual Desktop sites and resources. We recommend you use FQDN tags or service tags instead of URLs to prevent service issues. For more information, see Use Azure Firewall to protect Azure Virtual Desktop deployments. Service tags can be also used in User Defined Route ( UDR) to customize traffic routing behavior.Īzure Firewall supports Azure Virtual Desktop as a FQDN tag. Service tags can be used in both Network Security Group ( NSG) and Azure Firewall rules to restrict outbound network access. Microsoft manages the address prefixes encompassed by the service tag and automatically updates the service tag as addresses change, minimizing the complexity of frequent updates to network security rules. Service tags and FQDN tagsĪ virtual network service tag represents a group of IP address prefixes from a given Azure service. Azure Active Directory URLs can be found under ID 56, 59 and 125 in Office 365 URLs and IP address ranges. This list doesn't include URLs for other services like Azure Active Directory or Office 365. You'll need to repeat this process with the relevant URLs for each Azure region you want to deploy your session host virtual machines in. The URLs under event ID 3701 are region-specific. Unblock the URLs that you find under event ID 3701.Open Event viewer, then go to Windows logs > Application > WVD-Agent and look for event ID 3701.Ensure your session host virtual machines are registered to a host pool.If you prefer not to use this for agent-related traffic, here's how to find those specific URLs to use without specifying wildcards: You must use the wildcard character (*) for URLs involving service traffic. Please remove these URLs if you have previously explicitly allowed them: AddressĪuthentication to Microsoft Online Services and Microsoft 365 To avoid your session host VMs from showing Needs Assistance related to this, please allow *., if you have not already. We have finished transitioning the URLs we use for Agent traffic. ![]() Sign in to Microsoft Online Services and Microsoft 365ĭetects if the OS is connected to the internet The following table lists optional URLs that your session host virtual machines might also need to access for other services: AddressĪuthentication to Microsoft Online Services Please remove these URLs if you have previously explicitly allowed them: Address To avoid your session host VMs from showing Needs Assistance related to this, please allow *. if you have not already.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |