Tenant classification

To get started, let’s define tenant classification according to production and non-production workloads (NP) (PR). Workloads in the context of Microsoft Azure can be categorised as either Non-production (NP) or Production (PR), and this distinction is based on how Azure resources are utilised to fulfil the workloads in question. When I talk about workloads, I’m referring to the requirements for computational power and storage space, as well as the requirements for managing data while it is in motion.

Development, testing, and other tasks that are not absolutely necessary are often carried out under non-production workloads. It’s possible that these workloads don’t require the same amount of uptime and reliability that production workloads do, and they can also be less consistent.

On the other hand, production workloads are essential to the operation of an organisation and call for a high level of availability and dependability. It’s possible that these workloads entail mission-critical software and services that customers or other users access.

The categorization of workloads as either non-production or production can have an effect on the configuration and administration of Azure resources. Workloads that are not part of production might require a unique set of rules and resource tiers in comparison to production workloads.

Before publishing policies and custom roles to the production tenant, the Azure Governance Team builds and tests them in non-production tenants first. Each subscription that is part of the production tenant is assigned a category determined by the nature of the workload that it manages, and then a set of guidelines or restrictions is implemented for that particular subscription. Sandbox, Managed, Innovation, and Extension are some of the subscription types that come highly recommended by me.

The organisation of resources by employing environments, stages, and instances is distinct from tenant classification, which is dependent on whether or not a task is considered production or non-production.

The different phases that make up the production and distribution of a good or service are referred to together as stages. These phases include production, development, testing, and staging, amongst others. A different level of development or maturity is represented by the product or service at each stage.

Environments are an extension of stages and are used to further split the available resources inside a stage. They can also be used to add more content to a stage. For instance, you can have a number of development environments so that you can cater to the requirements of a variety of teams or projects. Additionally, you might have a number of testing settings so that you can accommodate a wide variety of testing procedures.

Instances are the smallest unit of granularity that can be utilised for deployment. Each instance of a product or service being deployed is an individual instance of that product or service. An instance is a specific version of a product or service that has been rolled out to a particular region or location. This can be thought of as a product or service “instance.”

You will be able to apply policies and controls at the right degree of granularity if you make use of these principles in order to organise and manage the resources in Azure in accordance with their purpose and use.

The workloads that are being managed are classified as either production or non-production by the tenant categorization system. On the other hand, the organisation of resources through environments, stages, and instances separates resources based on their purpose and use.

When it comes to defining Azure management groups, tenant classification is an essential aspect to take into consideration. You are able to organise your subscriptions and apply policies and governance controls at scale across your Azure setup by using management groups.

Create management groups that are in line with the organisational structure of your company and the governance standards you must meet by classifying your workloads as either production or non-production, and then assigning those workloads to the appropriate Azure subscriptions. This gives you the ability to apply different policies and controls to different sets of resources depending on the purpose and use of those resources.

For all of your production workloads, for instance, you might have a management group that is responsible for creating and enforcing policies with regard to high availability and security needs. On the other hand, you may establish a distinct management group for your non-production workloads, with policies that enable more leeway for flexibility and experimentation.

The choice of subscription type is also influenced by the tenant categorization, given that various subscription types come with a variety of service level agreements (SLAs) and resource constraints. It is possible to guarantee that the relevant sorts of subscriptions are utilised for each job if you allocate subscriptions to the appropriate category based on the classification of the workload.

The classification of tenants is an essential component of Azure’s governance and management, since it plays an important role in ensuring that resources are effectively organised and managed in accordance with their intended purpose and application.