Anish's Notebook

The intent is to create an appservice that is available inside a VNET. So we will create a vnet and put an appservice inside it. This Vnet will have 2 subnets. One that has the appservice and another one that will have a VM.. We need to make sure that this Appservice can be accessed only inside the VM (inside the same VNET)  1. Create a Vnet Total Address space is 256.. We split into 2 subnets 2. Create an Appservice in standard or above tier as the lower tiers dont support networking.  and select the Vnet and select the sub2 subnet 3. Create a Virtual Machine inside sub1. 4. Go to Appservices and onto the networking tab and select Access Restrictions Create a rule and select VNET and subnet that we created earlier. We can also specify IP Address. Then this appservice can be accessed by the specified IP's only. So this appservice can only be accessed within subnet 1. Which is where we have deployed the VM.. From Internet Inside VM (Subnet 1)

 1. Create 2 VM's inside 2 different VNets VM2 is inside vnet2 VM1 is inside vnet1 Step 2: Enable IIS in both VM's Step 3: Go to both VM's and add a default html page. Inside the below path add a text file. Click on save as and select all files as type and save the file as "Default.html". Try to access using the public IP. Since we have created the html page inside a folder called vm1 the path will be as shown below. Do the same for vm2 Step 4:  This will add a peering between Vnet1 and Vnet2 and vice versa. Get the Private IP for vm2 and try to access the URL inside VM1. Accessing VM1 inside VM2 using VM1's private IP.

 Create a function App and enable system assigned identity Create  a Keyvault and add a secret (Name in my case) Configure Access policies for the function app in keyvault Create an  access policy in Key Vault   for the application identity you created earlier. Enable the "Get" secret permission on this policy. Do not configure the "authorized application" or   applicationId   settings, as this is not compatible with a managed identity. https://docs.microsoft.com/en-us/azure/app-service/app-service-key-vault-references Key Vault references currently only support system-assigned managed identities. User-assigned identities cannot be used. We are granting our function app permissions to get and list all the secrets in this keyvault. Add Key Vault secrets reference in the Function App configuration Go to the keyvault and click on the secret we just created. Copy the secret identifier. We need to add this value to the function app configuration.  @Microsof...

Four core components of logic apps. First off, there are triggers. Triggers are the first step in a logic app that are used to start your logic app process. Inside your logic app you have one or more actions. Actions are the shapes that actually do things inside your logic app. You have connectors. Connectors are first-class citizens in Azure. Connectors are shared across logic apps, flow, and Power BI. Connectors are responsible for all your communication with third parties. Connectors are also Microsoft managed so you don't have to worry about maintaining these connectors, and last is flow control. Inside your logic apps you have several options for flow control. This includes do until, foreach, and even simple decision actions. LOGIC APP CREATION We will create a logic app that will start when an http request is received and based on the request body it will make decisions  Go to Logic Apps Designer and select the type of request to start the logic app. In this case we will star...