Top 10 Azure Policy



  1. Enforce like pattern for naming conventions
  2. Allowed region locations
  3. Allowed resource types
  4. Enforce a naming policy on Office 365 groups in Azure Active Directory
  5. Audit Key Vault vaults with no virtual network endpoints
  6. Audit diagnostic setting
  7. Use approved subnet for VM network interfaces
  8. Use approved vNet for VM network interfaces
  9. No network peering to Express Route network
  10. Allowed application gateway SKU

Comments

  1. legacymarbleandgranite10 December 2020 at 03:25

    Nice Post For me and It is a very different blog than the usual ones I visit. From this post, I get more knowledge and I read a lot of interesting content here. Thanks for sharing a knowledgeable post. Parcel Contract Negotiation

    ReplyDelete
  2. Laura Bush7 August 2021 at 11:33

    Thanks for publishing such great knowledge. You are doing such a great job. This info Parcel Contract Negotiation is very helpful for everyone. Keep it up. Thanks once again for sharing it.

    ReplyDelete
  3. shiprx7 May 2022 at 04:00

    Your blog took to me an entirely significant spot. It is a beneficial and factual article to enhance knowledge. Thanks for sharing an article like this.Parcel Contract Negotiation.

    ReplyDelete

Post a Comment

Popular posts from this blog

Deploy Palo Alto in Azure

Image
There are many ways to deploy Palo Alto Firewall in Azure. Out of those options today I will discuss how Palo Alto can be configured to protect your Azure workload. This setup is suitable for Proof of Concept only. Planning-Includes Minimum Requirement - Without HA Logical Diagram:  Create Virtual Network Name: PAN-VNet Address Space: 10.0.0.0/16 Subnet Name: Management Subnet Address Space: 10.0.1.0/24 Subnet Name: Untrust Subnet Address Space: 10.0.2.0/24 Subnet Name: Trust Subnet Address Space: 10.0.3.0/24 Resource Group: PA-VNet    Subnet Spin Web Server Virtual Machine  Name: SecureWebServices Image: Windows Server 2016 Resource Group: Services Network: PAN-VNet Subnet: Trust Role: Web Server (IIS) Installed Change NSG rules of Web Server to accept request on port 80, if you wish to test the web request. However, later on, this behaviour will be controlled through firewall. Spin Palo Alto Firewall Virtual Machine Na...
Read more

Demystifying System and User Define Routes of Azure

Image
As Virtual Network is created, Azure automatically create its own route tables for that Virtual Network, so that all the packets which enters the virtual network can traverse within its address prefix and leave the subnet for its destination. These are known as the Default Routes . We can’t modify these routes; however, we can add our custom routes on top of default routes for the traffic leaving the subnet. These custome route is known as User Define Routes . In this case, we are modifying the default behaviour of packets routing but still the internal and external routing of packet is done by virtual network to ensure that our packets are never hijacked.  In another word, we are adding routes and requesting virtual network to routes traffic in the way we want. So far its not possible to route the traffic independently bypassing the Azure Virtual Network routing mechanism and for security reason I do not think this will ever be possible. Common Use Case of UDR:  ...
Read more

Azure Private DNS Zone - App Service Environment V2 Step by step - Part 2

Image
Create a Private DNS Zone for App Service Environment  From the Azure Portal, Click at +, and search for Private DNS Zone, and select Create. Provide the resource group name and Zone name. Make sure it matches with the domain name used in web app running inside the Isolated Environment. Once is completed, create "A" record for '*', '*.scm", web app name, ftp, and publish.  I have not created pointer for ftp and publish.   We can bind this to Virtual Network. App Service Environment V2 Step by step - Part 2
Read more