What I was trying to achieve
I needed to use the MSOnline PowerShell Module to restore a deleted user from the Azure Active Directory (AAD) Recycle Bin. The replacement Module AzureAD does not (to my knowledge) have this functionality.
When trying to connect to AAD using the Connect-MsolService command, I received the following error:
Connect-MsolService : The Microsoft Online Services Module is not configured properly. Please uninstall and then reinstall the module.
I took the error messages advice, but to no avail.
The solution is in the registry…
Create a .reg file with the following content:
Windows Registry Editor Version 5.00
Import the reg file, then retry the command.
Thank you to user ‘Froggy’ who commented the solution at the following URL: https://stackoverflow.com/questions/36672088/how-do-i-correctly-install-the-powershell-msonline-module-in-windows-8-1-enterpr
I have an ExpressRoute circuit configured with a connection to a Version 2 (Resource Manager) Azure Virtual Network. I also have an additional Virtual Network in a different Subscription which I need to connect to the same circuit.
The instructions on connecting another Virtual Network in a different Subscription are a little confusing. It’s also worth noting that some of the parameters are different now with the latest version of the PowerShell Azure cmdlets. The original instructions may be found at this URL: https://azure.microsoft.com/en-us/documentation/articles/expressroute-howto-linkvnet-arm/#connect-a-virtual-network-in-a-different-azure-subscription-to-an-expressroute-circuit
Resource templates are a great concept, but are fraught with danger. Badly named resources and naming inconsistency across resources in different subscriptions can make it difficult to determine purpose.
If a resource such as a Virtual Network or a Storage Account is badly named in a resource template file, you may find that you have to rely on the icon pictures in the Azure portal to indicate what type of resources you are looking at.
What if you need to see at a glance:
- What region the resource belongs to i.e. Australia East or Australia Southeast?
- What environment the resource belongs to i.e. Production or Testing?
- What type of resource it is?
The problem comes from trying to keep the names meaningful and consistent. How do you ensure that your naming standards are adhered to?
In my case I would like to name resources as follows:
Did you know that when you delete an Azure Resource Group, it deletes all the resources in that group?
You have built a Resource Group in Azure that contains your infrastructure resources including:
- Virtual Network
- Network Security Groups (NSG)
- Storage account to hold diagnostic logging for the NSGs
The subnets may host your IaaS Virtual Machines, maybe define your DMZ and your reverse proxy. So questions around risk need to be asked including:
- How easy is it to delete a Resource Group?
- Who can delete a Resource Group?
- What can be done to protect a Resource Group?