Public preview: Service Tags for user-defined routing

You can now specify a [Service Tag](https://docs.microsoft.com/en-us/azure/virtual-network/service-tags-overview) for the address prefix parameter in a user-defined route for your route table. You can choose from tags representing over 60 Microsoft and Azure services to simplify route creation and maintenance. * You no longer need to manually update routes when services change or add to their list of endpoints. Routes with Service Tags will update automatically to include new changes. * This also eliminates the need for regularly updating routes based on the IP data in the weekly JSON file downloads that we provide. * This also helps reduce the likelihood of running into the routes per route table limit (400), which is common when configuring routing for multiple Microsoft and Azure services. By using Service Tags, you can avoid this, as the tag condenses all ranges for that service into one group. * For example, we list more than 4,500 prefixes that collectively represent the Azure address space. You can now use one route with the AzureCloud Service Tag, which will include all of these. The feature is available through REST, PowerShell, CLI and can also be used in ARM templates. This feature is not currently available through the Azure Portal. [Learn more](https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-udr-overview). * Virtual Network * Features * [ Virtual Network](https://azure.microsoft.com/en-gb/products/virtual-network/)