Graphical user interface, text, application, chat or text message Description automatically generated

Graphical user interface, text, application Description automatically generated

Hybrid Identity Administrator role is now available with Cloud Provisioning

Type: New feature

Service category: Azure AD Cloud Provisioning

Product capability: Identity Lifecycle Management

IT Admins can start using the new "Hybrid Admin" role as the least privileged role for setting up Azure AD Connect Cloud Provisioning. With this new role, you no longer have to use the Global Admin role to set up and configure Cloud Provisioning.

Note: Hybrid Identity Administrator

Users in this role can create, manage and deploy provisioning configuration setup from AD to Azure AD using Cloud Provisioning as well as manage Azure AD Connect, Pass-through Authentication (PTA), Password hash synchronization (PHS), Seamless Single Sign-On (Seamless SSO), and federation settings. Users can also troubleshoot and monitor logs using this role.

When deploying Azure Stack Hub in disconnected mode it is recommended to use certificates issued by an enterprise certificate authority. This is important because clients accessing Azure Stack Hub endpoints must be able to contact the certificate revocation list (CRL).

Table Description automatically generated

Create a new cloudadmin user named User2.

Add a new Azure Stack Hub user account in Azure Active Directory (Azure AD)

Before you can test offers and plans and create resources, you'll need a user account for the Azure Stack Hub user portal. You create a user account in your Azure AD tenant, by using the Azure portal or PowerShell.

Box 1: Administrator management endpoint

Note: The developers report high chargeback costs for the dev1 region.

Two integrated systems that are dedicated to application development and have the following configurations:

• The integrated systems are disconnected from the Internet. The workloads in the user subscriptions have Internet access.
• One integrated system has a region name of dev1, and the other has a region name of dev2.
• Both regions are used only by developers at Northwind Traders.

The request gets consumption details for the requested subscriptions and for the requested time frame. There is no request body.

This usage API is a provider API, so the caller must be assigned an Owner, Contributor, or Reader role in the provider's subscription.

Method, Request URI

GET https://{armendpoint}/subscriptions/{subId}/providers/Microsoft.Commerce.Admin/subscriberUsageAggregates?reportedStartTime={reportedStartTime} &reportedEndTime={reportedEndTime}&aggregationGranularity={granularity}&subscriberId={sub1.1}&api-version=2015-06-01-preview&continua

Arguments

* armendpoint

Azure Resource Manager endpoint of your Azure Stack Hub environment. The Azure Stack Hub convention is that the name of the Azure Resource Manager endpoint is in the format https://adminmanagement.{domain-name}. For example, for the Azure Stack Development Kit (ASDK), if the domain name is local.azurestack.external, then the Resource Manager endpoint is https://adminmanagement.local.azurestack.external.

* subId

Subscription ID of the user who makes the call.

* Etc.

Box 2: Get-AzsSubscriberUsage

Retrieve usage information

PowerShell

To generate the usage data, you should have resources that are running and actively using the system; for example, an active virtual machine (VM), or a storage account containing some data. If you're not sure whether you have any resources running in the Azure Stack Hub Marketplace, deploy a VM, and verify the VM monitoring blade to make sure it's running. Use the following PowerShell cmdlets to view the usage data:

• Install PowerShell for Azure Stack Hub.

• Configure the Azure Stack Hub user or the Azure Stack Hub operator PowerShell environment.

• To retrieve the usage data, call the Get-AzsSubscriberUsage PowerShell cmdlet:

Get-AzsSubscriberUsage -ReportedStartTime "2017-09-06T00:00:00Z"

Step 1: Notify all the users in the int1 region and schedule a maintenance window.

Step 2: Select the subscription that was used to perform the initial registration.

Note: You need to change the int1 region to use the capacity model.

Change the billing model and registration name of the int1 region.

The int1 region runs a high number of Windows virtual machines that use pay-as-you-use images.

Change billing model, how features are offered, or re-register your instance

This section applies if you want to change the billing model, how features are offered, or you want to re-register your instance. For all of these cases, you call the registration function to set the new values. You don't need to first remove the current registration.

# select the subscription used during the registration

Select-AzSubscription -Subscription '<Registration subscription ID from portal>'

# rerun registration with new BillingModel (or same billing model in case of re-registration) but using other parameters values from portal

Set-AzsRegistration -PrivilegedEndpointCredential $YourCloudAdminCredential -PrivilegedEndpoint $YourPrivilegedEndpoint -BillingModel '' -RegistrationName '<Registration name from portal>' -ResourceGroupName '<Registration resource group from portal>'

Step 3: Run the Set-AzsRegistration cmdlet.

You can use Set-AzsRegistration to register Azure Stack Hub with Azure and enable or disable the offer of items in the marketplace and usage reporting.

To run the cmdlet, you need:

A global Azure subscription of any type.

To be signed in to Azure PowerShell with an account that's an owner or contributor to that subscription.