Skip to main content

Registering an Azure Resource Provider with PowerShell

By
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}



Labels:

Comments

Post a Comment

Popular posts from this blog

How to list all the AD LDS instances on a server

By
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.
Post a Comment
Read more

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more