Page Comparison

...

You can use tenant scopes to:

1. Create restricted sets of resources for administrators

2. Share resources with a group of tenants and an optional tenant hierarchy

The following diagram shows an example of a tenant scopes that are in a hierarchy. The hierarchy contains the following scopes:

1. Multinational scope

2. Reseller1 scope

3. Customer1 scope

4. Dept1 scope

Edit each enterprise and assign the scope from the hierarchy as the Default scope of the enterprise. 

...

An administrator with the Customer1 scope Customer1Scope would manage the enterprises:

...

1. Customer1

...

...

1. Unit1

...

...

1. Unit2

...

...

Share resources to enterprises in a scope beneath your scope

...

• An administrator with the Multinational scope MultinationalScope could share templates and blueprints with users in all of the enterprises.

• An administrator with the Resellerl1 scope Resellerl1Scope could share to the enterprises in the scopes beneath their scope, which means the Customer1 scope Customer1Scope and the optional Dept1 scopeDept1Scope.

...

How to create a scope hierarchy

To create a scope hierarchy:

1. Create the top level scope, and set the Global scope as its parent

2. Add the enterprise in the top level scope

3. Create the second level scope and set the parent scope to be the top level scope

4. Add the enterprise to the second level scope

5. Continue to the next scope level, assign the parents

6. Add the enterprise

Continue to create scopes and add enterprises for the rest of the hierarchy

For the above example

1. Create the

...

1. scope called MultinationalScope and set the Global scope as its parent

2. Add the Multinational enterprise

...

1. . 

2. Create the

...

1. scope called Reseller1Scope. Set the parent scope of

...

1. Reseller1Scope to MultinationalScope. 

2. Add the Reseller1 enterprise

...

1. .  

...

1. Create Customer1Scope and set its parent scope as

...

1. Reseller1Scope. 

...

1. Add the

...

1. Customer1

...

1. and

...

1. Unit1 and Unit2

...

1. enterprises

2. You can also create the

...

1. Dept1Scope or even allow your customers to create their own sub scopes

...

The reseller enterprise can provide public cloud credentials to customers. And the reseller will receive aggregate billing reports for customers. In the above example, "Customer1" would be a reseller in its scope and scope hierarchy.

To mark a reseller:

1. Edit the tenant that represents reseller, at the top of the scope hierarchy

2. Set the Reseller1 scope as the default scope for the enterprise. This will be the scope where the enterprise is the reseller

   1. The platform will also apply the default scope to new users in this enterprise

3. Select the reseller option

This tenant will be marked with a (R) in the tenant list, indicating to indicate that the enterprise is a reseller.

...

The enterprise at the top of a customer hierarchy can be set as the key node for data aggregation. For example, you can bill services to this main enterprise, and usage to the sub-tenant enterprises below it. As each enterprise can only have one public cloud account or subscription, if your tenant has multiple accounts, such as Azure plans, then you should create one sub-tenant enterprise for each subscription.

In the above example, "Customer1" would be a key node in its scope and scope hierarchy.

To mark a key node:

1. Edit the tenant that represents the head office or equivalent, at the top of its scope hierarchy (Unit1, Unit2 are in the same scope, and Dept1 is in a lower scope) 

2. Set the top level scope as the default scope for the enterprise. This will be the scope where the enterprise is the key node

   1. The platform will also apply the default scope to new users in this enterprise, but you can edit this scope, for example, to set a scope with only the user's enterprise

3. Select the Key node option

...

A key node tenant will be marked with a (K) in the tenant list.

...