Thanks for submitting this request. In the meantime, you can use the Advanced Application Restart feature to restart specific instances that are “misbehaving”.
Thank you for the feedback. The product team is aware of this need and will consider it if resourcing allows.Mike commented
+1 I too have CosmosDB scripts that should be in an automation like setting and PS doesn't deliver the same functionality (eg. dealing with RU/s).
Thank you for all the votes and feedback. We have started work on this and the capability will be supported soon. If you would like to get in touch with us to discuss your scenarios, please fill this form: https://aka.ms/ApplicationGatewayCohort
We’re addressing this need with “Service Tags” which allow network security group rules to refer to Azure services such as “Storage” or “Sql” and the list of IP addresses is maintained transparently by the Azure platform. See here for more information: https://docs.microsoft.com/en-us/azure/virtual-network/security-overview#service-tags
We’ll be adding tags for additional Azure services over time.Mike commented
I have a case where we want to enable a Dynamics365/CRM solution and in addition to a coded NSG rule to allow Dynamics365 IPs, we also have to allow ALL Azure IPs in. For environments that have sensitive data it's important to be able to disallow traffic from untrusted sources (eg. any ol' Azure subscription vs. O365, Exchange, etc.).
Microsoft Azure Datacenter IP Ranges are required for Dynamics 365 organizations on version 9, and higher. To view the required IP ranges for the Microsoft Azure Datacenter, please see the following link..."