官术网_书友最值得收藏!

How is access to Azure organized?

In the previous sections of this chapter, we've had an overview of the Azure platform. Now let's dig a bit deeper.

The first point in our discovery journey— How is access to the Azure platform organized?

As long as we look at Azure from our personal point of view, the answer is simple—our entire world consists of an Azure account, a subscription and the direct or indirect handling of Azure resources, as shown here:

But if we look at the situation from the perspective of an enterprise, it becomes much more complicated, as shown in the next figure. The reason for this is Microsoft's attempt to delineate your company with an Azure enrollment as precisely as possible.

Let's have a look—the high-level element in the figure is now the enterprise element linked to the Enterprise Administrator's role. Here, the most comprehensive and highest rights exist. An Enterprise Administrator is allowed to do everything within the Azure enrollment.

The rights of the Enterprise Administrator include:

  • If necessary, he/she can appoint additional Enterprise Administrators
  • It defines the so-called departments and appoints corresponding department administrators
  • It can set up accounts as required

The Enterprise Administrator is also the only person who can access all consumption and cost data at every level of the Azure enrollment.

The next element is departments (linked to the Department Administrator's role)—with the creation of departments, you can subdivide your enrollment into logical units. Even if the term department suggests something different, you have given yourself flexibility in terms of how the elements are divided.

The decision on how elements are classified is actually made based on the following:

  • Functional aspects (in fact, according to the organizational structure)
  • Business interests (that is according to the project's business)
  • Geographical aspects (different locations, branch offices, and so on)

Let's go to the Department Administrators—they have the ability to create accounts within their department and, if necessary, can create a cost center (for a complete cost control).

From the next level, everything is as usual (Azure account, subscriptions, Azure resources and so on):

主站蜘蛛池模板: 浦江县| 略阳县| 手游| 锡林郭勒盟| 无棣县| 辛集市| 佛坪县| 灵璧县| 布尔津县| 南郑县| 冀州市| 泰宁县| 资溪县| 东乡族自治县| 新余市| 囊谦县| 集安市| 镇江市| 西华县| 南木林县| 长春市| 承德市| 炎陵县| 屯门区| 元朗区| 眉山市| 宜州市| 富民县| 德钦县| 富锦市| 集贤县| 长丰县| 辽宁省| 卓资县| 镇宁| 尼勒克县| 连平县| 定远县| 广安市| 庆安县| 会理县|