Skip to main content

Registering an Azure Resource Provider with PowerShell

Azure seems to be the cloud that just keeps building and building.

Resource providers allow Azure to provide services.  For example, virtual machines utilize the Microsoft.Compute resource provider to provide services to Azure so you can have a virtual machine.  Checkout this article to see what the Microsoft.Compute exposes to Azure: https://docs.microsoft.com/en-us/azure/role-based-access-control/resource-provider-operations#microsoftcompute

It is not that exciting to look at.  What is exciting is what resource providers can do.  Azure acts as an orchestrator.  The resource providers tell Azure what they can do and they perform all the work.  Each resource must be registered with the subscription before Azure can utilize them. 

Just remember that you cannot unregister a resource provider if any Azure asset in your subscription is using it.

(Note: The following assumes that you are using VSCode and are logged into your Azure subscription.

Our goal is to register the Microsoft.Insights provider.


 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
# Show all available Resource Providers
Get-AzResourceProvider -ListAvailable | 
  Select-Object -Property ProviderNamespace, RegistrationState

# Show all available resource providers in a specific region.
$region = 'west us'
Get-AzResourceProvider -ListAvailable -Location $region


#Display the status of a particular resource provider
$providerNamespace= 'Microsoft.Insights'
Get-AzResourceProvider -ProviderNamespace $providerNamespace -Location $region

# Register a provider 
Register-AzResourceProvider -ProviderNamespace $providerNamespace

Here is the result:


ProviderNamespace : microsoft.insights
RegistrationState : Registering
ResourceTypes     : {components, components/query, components/metrics, components/events}
Locations         : {East US, South Central US, North Europe, West Europe}




PS C:\> Get-AzResourceProvider -ProviderNamespace $providerNamespace 

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {components}
Locations         : {East US, South Central US, North Europe, West Europe}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {components/query}
Locations         : {East US, South Central US, North Europe, West Europe}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {components/metrics}
Locations         : {East US, South Central US, North Europe, West Europe}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {components/events}
Locations         : {East US, South Central US, North Europe, West Europe}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {webtests}
Locations         : {East US, South Central US, North Europe, West Europe}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {scheduledqueryrules}
Locations         : {West Central US, East US, West Europe, Central India}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {components/pricingPlans}
Locations         : {East US, South Central US, North Europe, West Europe}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {migrateToNewPricingModel}
Locations         : {East US, South Central US, North Europe, West Europe}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {rollbackToLegacyPricingModel}
Locations         : {East US, South Central US, North Europe, West Europe}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {listMigrationdate}
Locations         : {East US, South Central US, North Europe, West Europe}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {logprofiles}
Locations         : {}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {migratealertrules}
Locations         : {}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {metricalerts}
Locations         : {Global}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {alertrules}
Locations         : {West US, East US, North Europe, West Europe}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {autoscalesettings}
Locations         : {West US, East US, North Europe, South Central US}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {eventtypes}
Locations         : {}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {locations}
Locations         : {East US}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {locations/operationResults}
Locations         : {}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {vmInsightsOnboardingStatuses}
Locations         : {}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {operations}
Locations         : {}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {diagnosticSettings}
Locations         : {West US, East US, North Europe, West Europe}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {diagnosticSettingsCategories}
Locations         : {West US, East US, North Europe, West Europe}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {extendedDiagnosticSettings}
Locations         : {West US, East US, North Europe, West Europe}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {metricDefinitions}
Locations         : {East US, West US, West Europe, East Asia}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {logDefinitions}
Locations         : {West US, East US, North Europe, West Europe}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {eventCategories}
Locations         : {}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {metrics}
Locations         : {East US, West US, West Europe, East Asia}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {metricbatch}
Locations         : {}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {metricNamespaces}
Locations         : {East US, West US, West Europe, East Asia}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {actiongroups}
Locations         : {Global}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {activityLogAlerts}
Locations         : {Global}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {baseline}
Locations         : {East US, West US, West Europe, East Asia}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {metricbaselines}
Locations         : {East US, West US, West Europe, East Asia}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {calculatebaseline}
Locations         : {}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {workbooks}
Locations         : {West Europe, South Central US, East US, North Europe}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {workbooktemplates}
Locations         : {West Europe, South Central US, East US, North Europe}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {myWorkbooks}
Locations         : {West Europe, South Central US, East US, North Europe}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {logs}
Locations         : {East US, East US 2, West US, Central US}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {transactions}
Locations         : {East US, South Central US, North Europe, West Europe}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {topology}
Locations         : {East US, South Central US, North Europe, West Europe}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {privateLinkScopes}
Locations         : {Global}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {privateLinkScopes/privateEndpointConnections}
Locations         : {Global}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {privateLinkScopes/privateEndpointConnectionProxies}
Locations         : {Global}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {privateLinkScopes/scopedResources}
Locations         : {Global}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {components/linkedstorageaccounts}
Locations         : {East US, West Central US, South Central US, North Europe}

ProviderNamespace : microsoft.insights
RegistrationState : Registered
ResourceTypes     : {privateLinkScopeOperationStatuses}
Locations         : {Global}



Comments

Popular posts from this blog

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix.  This customization deals with Group Policy and PowerShell.  For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material.  I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO.  This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy.  One organization in the crowd had over 5,000 Group Policies.  In an environment like that, the comment section can be priceless.  I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique   # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers.  The first command creates a collection with 2 duplicates of both 1 and 2.   The second command creates another collection with the duplicates filtered out.  The Compare-Object cmdlet will first find items that are diffe

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.