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

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

By
This was an interesting observation from one of my Windows Server 2012 classes.  While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted.  When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places.  First off in the Active Directory Administrative Center.  This is what caused the initial confusion.  Take a look.  This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3.  Test3 is a valid, functioning user account.  Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...
Post a Comment
Read more

Sticky Key problem between Windows Server 2012 and LogMeIn

By
This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .
6 comments
Read more

Backup and Restore AD LDS with DSDBUTIL.exe

By
Active Directory Lightweight Directory Services allow you to create a directory service that allows applications to have access to user accounts, groups, and authentication similar to Active Directory Domain Services.  The big advantage here is that the schema of the directory service will not be bound by the rules of an Active Directory database.  Exchange 2007/2010, for example, use an instance of AD LDS on the Edge Transport Server to provide for user authentication from the internet.  Because your Active Directory database is not exposed to the internet, this is more secure. Applications will handle most of the dirty work should they require AD LDS.  You may want to make sure the database is being backed up and also have a restore plan in place.  Should the database become corrupt, the application that uses that database will fail.  This document will walk you through backing up and restoring an instance of AD LDS using the dsdbutil.exe command. Fi...
6 comments
Read more