Central IP Object usable for ALL Azure Resources

In this new feature (ex : Azure IP Object management) user can create IP Object (List of Ips or Subnet) this object can be added in any Azure Resources who have a Firewall (Azure SQL, Storage Account, WebApp,...)

For Exemple:
You create an Object "Company Public IPs" and you add in this object All your company Public IP.
In your Azure resources Firewall (WebApp, AzureDB, NSG,...) you specify this Object to allowing access.

If tomorrow you need to add a new public IP you just need to add this new public IP in your "Company Public IPs" Object and all resources link to this object will allow this new IP (cf: diagram)

Matthieu

We only have a execute stored procedure in ADFv2. But most of the time we don't want to create stored procedure for all of the primary ETL tasks, such as counting the no. of records from a table, Updating data into tables, creating tables, etc. There are many such activities need T-SQL Execution. It would be great if we have Execution SQL option.

ADFv2 have the option to use variety of RDBMS source and sink systems such as MySQL, Oracle, etc., . ESQL would be the powerful task to have in Azure Data Factory V2 to be used in all of the RDBMS source / sink systems, as SQL is compatible for all of them.

Some of the other points to have ESQL task is highlighted,

1. Stored procedures are not the effective object to understand, debug complex sql code written within. With E-SQL, a large complex SP could be split at many places in the ETL flow and graphically represented to easy understanding. - Graphical representation is the core feature for any ETL tool.

2. Version management - For example. A create table script could be placed on a blob storage. which can be used as a source for E-SQL task. This helps to manage the table object in terms of adding additional columns in future could be done from blob / file storage

3. When SSIS is rebuilt on Azure Data Factory (which is the ultimate goal for Azure Data Factory V2). ESQL is used quite commonly in SSIS. By having this in ADF, it helps for quicker development

Additional feature with E-SQL could be great is to use source and sink systems. For example, getting data from Oracle source system and which need to perform a lookup with SQL Sink, and load them back to SQL Sink. If we have the option on ESQL to use both source and sink. It would be more powerful.

Thanks and Regards,
Vijay

Currently there is no way to sepcify which storage replication is wanted when you create a Recovery Services Vault via ARM templates.

The default when spinning up a vault is GRS, and the only way to change it is to log into the portal and choose LRS before any backups have been applied.

The fact that the type of storage replication cannot be changed after a backup has been set does not help the situation.

This makes automating infrastrucutre builds painful as I have to login and change the setting in the portal before i am able to continue adding machines to the vault.

The documentation for the Vault is here:
https://docs.microsoft.com/en-us/azure/templates/microsoft.recoveryservices/vaults

If this is already available then please update the docs and the Quick start templates to include it!

If its not available then please add it to ARM!

Quick Start Template :
https://github.com/Azure/azure-quickstart-templates/tree/master/101-recovery-services-vault-create

Prevent Creation of Legacy Machine Learning Workspace Commitment Plans and classic web services so Tags can be Enforced.

Our organization sets a Tag policy on resource groups so that newly created resources within that resource group will inherit tags. The main tag is 'Department Code', and is used for Chargeback for resource usage. Any Machine Learning 'classic' web services, that were created using the Machine Learning Studio portal will be created outside of the standard tagged resource group and thus, will not inherit standard tags used for Chargeback.

We also need a migration method for existing classic web services to be migrated to ARM web services, which is currently not supported by Microsoft. We will need to delete deployed instances from classic web services and deploy web services instead of classic web service from ML studio, and this has to be done one experiment at a time.

Currently we are operating in a shared subscription model where each app team is assigned specific resource group(s) and their access is scoped at this level. For them to open premier tickets from ARM, they have to be added as Support Request Contributor at the subscription level.
This enables visibility to all resource groups in the subscription and impacts the experience of the user. The complaints I have received are "Now I have to search for my resource group" and "I thought we had our own subscription"

The concept of resource groups is great but loses value when users have to be added to the subscription level