DEV Community: Umar Abdulqadri

Create an Azure Policy

Umar Abdulqadri — Thu, 05 May 2022 22:00:06 +0000

Task 1: Create a Policy assignment

Sign in to the Azure portal.
search for and select Policy, under the Authoring section click Definitions. Take a moment to review the list of built-in policy definitions. For example, in the Category drop-down select only Compute. Notice the Allowed virtual machine size SKUs definition enables you to specify a set of virtual machine SKUs that your organization can deploy.
Return to the Policy page, under the** Authoring** section click Assignments. An assignment is a policy that has been assigned to take place within a specific scope. For example, a definition could be assigned to the subscription scope.
Click Assign Policy at the top of the Policy - Assignments page.
On the Assign Policy page, keep the default Scope
On the Parameters tab, select Japan West. Click Review + create, and then Create.

Note: A scope determines what resources or grouping of resources the policy assignment applies to. In our case we could assign this policy to a specific resource group, however we chose to assign the policy at subscription level. Be aware that resources can be excluded based on the scope configuration. Exclusions are optional.

Note: This Allowed Locations policy definition will specify a location into which all resources must be deployed. If a different location is chosen, deployment will not be allowed. For more information view the Azure Policy Samples page.

The Allowed locations policy assignment is now listed on the Policy - Assignments pane and it is now in place, enforcing the policy at the scope level we specified (subscription level).

Task 2: Test Allowed location policy

In the Azure Portal, search for and select Storage accounts, and then click + Create.
Configure the storage account letters and digits such that the name is globally unique. Leave the defaults for everything else.
Click Review + create and then click Create.

You will receive the deployment failed error stating that resource was disallowed by policy, including the Allowed locations policy name

.
Task 3: Delete the policy assignment
In this task, we will remove the Allowed location policy assignment and test.

We will delete the policy assignment to ensure we are not blocked on any future work we wish to do.

search for and select Policy, and then click your Allowed locations policy.

Note: On the Policy blade, you can view the compliance state of the various policies you have assigned.

Note: The Allowed location policy may show non-compliant resources. If so, these are resources created prior to the policy assignment.

Click Allowed Locations It will open an Allowed locations Policy Compliance window.

Click Delete Assignment in the top menu. Confirm you wish to delete the policy assignment by clicking Yes

Try to create another storage account to ensure the policy is no longer in effect.

Note: Common scenarios where the Allowed locations policy can be useful include:

Cost Tracking: You could have different subscriptions for different regional locations. The policy will ensure that all resources are deployed in the intended region to help cost tracking.
Data Residency and Security compliance: You could also have data residency requirements, and create subscriptions per customer or specific workloads, and define that all resources must be deployed in a particular datacenter to ensure data and security compliance requirements.
Congratulations! You have created an Azure Policy to restrict deployment of Azure resources to a particular datacenter.

Note: To avoid additional costs, you can optionally remove this resource group. Search for resource groups, click your resource group, and then click Delete resource group. Verify the name of the resource group and then click Delete. Monitor the Notifications to see how the delete is proceeding.

Manage resource locks

Umar Abdulqadri — Thu, 05 May 2022 00:43:19 +0000

Task 1: Adding a Lock to the resource group and test deletion

Sign in to the Azure portal.
In the Azure portal, navigate to the resource group umarproject.
You can apply a lock to a subscription, resource group, or individual resource to prevent accidental deletion or modification of critical resources.
In the Settings section, click Locks, and then click + Add fill the details and click ok.

Click Overview and click Delete resource group. Type the name of the resource group and click OK. You receive an error message stating the resource group is locked and can’t be deleted.

Task 2: Test deleting a member of the resource group

Search for and select Storage accounts, and then + Create
On the Storage Accounts page +Create, pick the name of the resource group that was lock earlier and then fill in the storage name. Leave the defaults for everything else. as shown in the below image

Click Review + Create to review your storage account settings and allow Azure to validate the configuration.
Once validated, click Create. Wait for the notification that the account was successfully created.
Wait for the notification that the storage account was successfully created.
Access your new storage account and from the Overview pane, click Delete. You receive an error message stating the resource or its parent has a delete lock.

Note: Although we did not create a lock specifically for the storage account, we did create a lock at the resource group level, which contains the storage account. As such, this parent level lock prevents us from deleting the resource and the storage account inherits the lock from the parent.

Task 3: Remove the resource lock

Return to the umarproject resource group blade and, in the Settings section, click Locks.

Click Delete link to the far right of the umarproject entry, to the right of Edit.

Return to the storage account blade and confirm you can now delete the resource.

*Congratulations! You created a resource group, added a lock to resource group and tested deletion, tested deleting a resource in the resource group, and removed the resource lock.
*
**Note: **To avoid additional costs, you can optionally remove this resource group. Search for resource groups, click your resource group, and then click Delete resource group. Verify the name of the resource group and then click Delete. Monitor the Notifications to see how the delete is proceeding.

Implementation of Azure IoT Hub

Umar Abdulqadri — Wed, 04 May 2022 23:45:29 +0000

Task 1: Creating IoT Hub

Sign in to the Azure portal.
search for and select IoT Hub
click Create and fill in the fields as shown in the image below

Go to the Management tab, and use the dropdown to set the Pricing and scale tier to S1: Standard tier.
Click the Review + create button.
Click the Create button to begin creating your new Azure IoT Hub instance.

Wait until the Azure IoT Hub instance is deployed.

Task 2: Adding an IoT Device

When the deployment has completed, click Go to resource from the deployment blade. Alternatively, search for and select IoT Hub and locate your new IoT Hub instance
Go to resource scroll down to the Device management section and click Devices. Then, click + Add Device.

Provide a name for your new IoT device, qadriumar, and click the Save button. This will create a new IoT device identity in your Azure IoT Hub.

If you do not see your new device, Refresh the IoT Devices page.
Select qadriumar and copy the Primary Connection String value. You will use this key in the next task to authenticate a connection to the Raspberry Pi simulator.

Task 3: Testing the device using a Raspberry Pi Simulator

Open a new tab in the web browser and type this shortcut link (https://aka.ms/RaspPi) It will take you to a Raspberry Pi Simulator site. When done select “X” to close the pop-up window.
In the code area on the right side, locate the line with ‘const connectionString =’. (line 15)Replace it with the connection string you copied from the Azure portal. Note that the connection sting includes the DeviceId (qadriumar) and SharedAccessKey entries.

Click Run (below the code area) to run the application. The console output should show the sensor data and messages that are sent from the Raspberry Pi simulator to your Azure IoT Hub. Data and messages are sent each time the Raspberry Pi simulator LED flashes.
Click Stop to stop sending data.

Return to Azure Portal
Switch the IoT Hub Overview blade and scroll down to the IoT Hub Usage information to view usage. Change your timeframe in the show data for last to see data in the last hour.

Congratulations! You have set up Azure IoT Hub to collect sensor data from an IoT device.

Note: To avoid additional costs, you can optionally remove this resource group. Search for resource groups, click your resource group, and then click Delete resource group. Verify the name of the resource group and then click Delete. Monitor the Notifications to see how the delete is proceeding.

Thank you all

How to create blob storage in Azure

Umar Abdulqadri — Tue, 03 May 2022 21:08:04 +0000

Creating a storage account

Sign in to Azure portal
From the all service blade search for storage account
Click on create fill the resource and storage account name as shown in the below image proceed to create and review
once validated click on create and wait for the storage to deployed. Search for storage to verify if the storage account name entered earlier is created

*Working with blob storage *

Click the name of the new storage account(qadriumarr), scroll to the Data storage section in the left menu, and then click Containers.

Click + Container and complete the information. When done click Create as shown in the below images

Back in the Portal, click on (qadriumarr) , and then select Upload.

Browse for the image file you just saved on your local computer. Select it and then select upload.

Click the Advanced arrow, leave the default values but review the available options, and then click Upload.

Note: You can upload as many blobs as you like in this way. New blobs will be listed within the container.

Once the file is uploaded, right-click on the file and notice the
options including View/edit, Download, Properties, and Delete.

Monitoring the created storage account

Return to the storage account blade and click Diagnose and solve problems.

Explore some of the most common storage problems. Notice there are multiple troubleshooters here.

On the storage account blade, scroll down to the Monitoring section and click Insights. Notice there is information on Failures, Performance, Availability, and Capacity. as shown in the below images

Thank you allll

Creating and implementing key vault in Azure

Umar Abdulqadri — Tue, 03 May 2022 16:38:15 +0000

The below steps are used in creating and implementing key vault in Azure portal

Sign in to Azure portal
search for and select Key vaults, then select Create

Fill in the resource group, key vault name and click on create as shown in the below image

click on go to resource

note take note of your Vault URL

ADDING A SECRET TO THE VAULT CREATED ABOVE

Go to setting, click on secret and click generate/import as shown in the below image

Fill in name and vault value

Select the secret you just created, note the the Secret Identifier. This is the url value that you can now use with applications. It provides a centrally managed and securely stored password.
Click the button Show Secret Value, to display the password you typed earlier.

Thank you all and i hope this article help