A solid governance is the foundation of a successful Azure implementation. I often refer to it as “freedom within the frame”. As an organization, you configure the rules of the game, e.g. allowed locations, no public IPs, restricted service tiers…...
Lately, I was involved in auto-provisioning a complete Azure governance setup. The automation was done through Azure CLI, as this offered the most flexible solution for my customer. Policy definitions were created via the az policy definition create command. While...
In a previous post, I explained why and how you could enforce the usage of product subscriptions within Azure API Management. As I was not entirely happy about the solution, I invested a little more time to check if Azure Policy could achieve the same result! And...
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.