There are 3 components used for Azure Identity Authorization Management: Azure Active Directory Azure Role-Based Control Scopes Azure Active Directory It belongs to top of resources hierarchy, in which identify and prove you are who you are saying you are. Once the identity has been resolved, the role and permissions can set to that identity. Each identity in Azure in known as security principal because identity can represents users, applications and so on....
There is a resources organization in Azure applied at 5 levels, such as: Tenant Management Group Subscriptions Resource Group Resources One of the advantages of that organization is a centralize manner to set up permissions. Permissions applied in one level will be replicated to the lower levels. For example, access policy established for a set of identities and roles to a specific subscription means all resources belong to it will conform with those policies....
Cloud Computing means use compute resources from someone else and somewhere else in remote data centers around the world. There are some characteristics around this subject, such as: Fault Tolerance: The approach for replicate the solution more than one place in order to reduce downtime to consume those services when you face with any crash. It is like “backup”, applied for applications, data and so on and sor forth. High Availability: The purpose to take closer users that services they will consume for....
There are two ways in order to authenticate in Azure using Azure CLI: Interactive mode Service Principal mode Interactive mode az login It allows you authenticate in Azure launching the Azure’s authentication page in a browser to manually provide the username and password. Service Principal mode az login --service-principal It is ideal for scenarios used by automated tools. You will need to create one (if it does not exist yet) by either az ad sp create command or az ad sp create-for-rbac command, last giving the according permissions for the Azure resources....
Some of the advantages using code to provisioning virtual machines are: consistency: you are able to create virtual machines with the same characteristics regardless the amount required to that deploy. Besides that, you can follow the changes for this resource using system version control. automation: due to the steps are the same to deploy that resource, they are candidates to automate them, helping to repeat themselves every time as needed. It avoids make some mistakes whereas could appear when apply those steps manually....
Azure Spot instance is a setting that allows Azure to stop and deallocate the virtual machine in order to provide compute capacity to Azure for whatever reason.
In a high level what Azure virtual machine is composed of, the one’s components are: Resource Group: a virtual machine is deployed into a Resource Group, that latter contains an Azure region. Deploying a virtual machine for that Resource Group means to choose in deliver a phisically virtual machine in that location in order to take closer users and/or applications will use the services hosted in it. Size: when building a virtual machine, it is necessary pick one size from a pre-configured list based on a number of CPU cores, amount of RAM and also disk performance capabilities....