Tips & Tricks (Part 3): Get The Most Out of Azure!
Here are some Tips & Tricks that will hopefully help you to get MORE out of Microsoft Azure.
If you’ve ever wanted to quickly organize Azure Resources then you can utilize tags to do so. For example, if you’d like to have a set of Resources for “Production” and another for “Dev”, then you can quickly do that.
Tags allow you to annotate your resources with information that you can later use to organize those resources logically. Tags also show up on your billing data so you can use them for both resource and cost management. We are improving the tagging experience and now you can tag, or untag, multiple resources with a single interaction, as shown in the image below.
Head over to the Azure Portal and select service.
NOTE: Tags are user-defined key/value pairs which can be placed directly on a resource or a resource group.
As an administrator, you may need to lock a subscription, resource group, or resource to prevent other users in your organization from accidentally deleting or modifying critical resources.
You can set the lock level to CanNotDelete or ReadOnly. In the portal, the locks are called Delete and Read-only respectively.
- CanNotDelete means authorized users can still read and modify a resource, but they can't delete the resource.
- ReadOnly means authorized users can read a resource, but they can't delete or update the resource. Applying this lock is similar to restricting all authorized users to the permissions granted by the Reader role.
To add a lock, select Add. If you want to create a lock at a parent level, select the parent. The currently selected resource inherits the lock from the parent. For example, you could lock the resource group to apply a lock to all its resources.
Give the lock a name and lock level. Optionally, you can add notes that describe the lock.
To delete the lock, select the ellipsis and Delete from the available options.
When you apply a lock at a parent scope, all resources within that scope inherit the same lock. Even resources you add later inherit the lock from the parent. The most restrictive lock in the inheritance takes precedence.
These steps show you how to use Azure PowerShell commands to migrate infrastructure as a service (IaaS) resources from the classic deployment model to the Azure Resource Manager deployment model.
Here are a few best practices that we recommend as you evaluate migrating IaaS resources from classic to Resource Manager:
- Read through the supported and unsupported features and configurations.
VMs in VNet
- Scope of migration is VNet
- Platform migrates the VNet along with the VMs in that VNet
- No VM downtime during this migration
VMs not in VNet
- Scope of migration is Cloud Service
- VM will incur downtime during the migration
- VMs will move into a VNet in the Resource Manager stack
Azure Storage Explorer allows you to easily manage the contents of your storage account. It comes complete with features such as: upload, download, and manage blobs, files, queues, tables, and Cosmos DB entities.
- Use a connection string or a shared access signature URI .
- Switch over to my Azure Storage account that I want to work with and look under Settings, then Access Keys and copy the connection string to my clipboard.
- Paste that into Azure Storage Explorer and now have access to the data.
It is absolutely terrific tool that works on various platforms (Windows, Mac, Linux) and keep in mind that it works with blobs, files, queues, tables, and Cosmos DB entities.
Please read more about Storage Explorer here: 3 TOP Reasons Why You Should Use FREE Azure Storage Explorer?!
I am really excited to show you Azure Tips and Tricks in part 3. I am planning to write many more bite-sized articles like this. Please have a look at other articles as well.
Please have a look at part 1 here - LINK
Please have a look at Part 2here - LINK
Thanks
Susanth