{"id":6161,"date":"2015-09-24T11:34:27","date_gmt":"2015-09-24T09:34:27","guid":{"rendered":"http:\/\/dollarunderscore.azurewebsites.net\/?p=6161"},"modified":"2016-09-06T22:52:15","modified_gmt":"2016-09-06T20:52:15","slug":"managing-office-365-and-azure-ad-with-azure-automation","status":"publish","type":"post","link":"https:\/\/p0wershell.com\/?p=6161","title":{"rendered":"Managing Office 365 and Azure AD with Azure Automation"},"content":{"rendered":"

Update:<\/strong>
\nThe Windows Azure Active Directory Module that was in preview when this was posted has been released and can be deployed straight to Azure Automation from this page: http:\/\/www.powershellgallery.com\/packages\/MSOnline\/1.0<\/a><\/p>\n

The original post follows:<\/em><\/p>\n

The Azure AD PowerShell module<\/a> have some dependencies that historically made it fail in Azure Automation. In fact, it’s the most upvoted suggestion<\/a> for Azure Automation at the time of writing this.<\/p>\n

But very recently a public preview of a new version<\/a> of the module was released where the authentication part has been changed to use ADAL<\/a> instead, which seems to fix this issue!<\/p>\n

This is how you can test it yourself:<\/p>\n

First, you need to uninstall any previous version of the module you might have. If you can, go ahead and uninstall the Microsoft Online Services Sign-In Assistant as well to make sure the new module works as expected (the dependency on this service is now removed).<\/p>\n

Then go to the download page<\/a> for the preview version of module, download it and install it. The installation procedure is very simple:
\n\"Wizard1\"<\/a><\/p>\n

Click next…<\/p>\n

\"Wizard2\"<\/a><\/p>\n

Read the license terms, and check the box if you agree. Click next again…<\/p>\n

\"Wizard3\"<\/a><\/p>\n

Choose an installation path (this actually not where the module currently ends up though, just the EULA-file…).<\/p>\n

\"Wizard4\"<\/a><\/p>\n

Click Install to begin the installation, and confirm the UAC-prompt if you get one.<\/p>\n

\"Wizard5\"<\/a><\/p>\n

The installation runs…<\/p>\n

\"Wizard6\"<\/a><\/p>\n

And finally, just click Finish and the module is installed.<\/p>\n

Now open a PowerShell prompt, and run the following commands:
\nImport-Module MSOnline
\nGet-Module MSOnline | Format-List<\/p>\n

In the property “Path”, you’ll see where the module was installed, in my case it was “C:\\WINDOWS\\system32\\WindowsPowerShell\\v1.0\\Modules\\”:
\n\"ModuleInstallPath\"<\/a><\/p>\n

Go to that folder and zip the folders MSOnline and MSOnlineExtended, easiest way is probably to right-click on the folder, choose “Send to”, and then “Compressed (zipped) folder”, do this for both (one at a time). Should look something like this:
\n\"SendToZip\"<\/a><\/p>\n

It will prompt you to place the zipped files on your desktop instead of the current folder, which is a good idea, so click “Yes” \ud83d\ude42
\n\"PlaceOnDesktop\"<\/a><\/p>\n

You can now import those zip-files into Azure Automation. I recommend that you do this in the classical portal (I’ve had some issues when importing modules in the preview portal).<\/p>\n

First, go to your automation account, then go to assets, and then click \u201cImport Module\u201d at the bottom:
\n\"AzurePortal_ImportModule\"<\/a><\/p>\n

Browse to your zipped module and click open:
\n\"AAPortalBrowseChooseModule\"<\/a><\/p>\n

Click complete in lower right corner:
\n\"ImportModuleDialogClassicPortal\"<\/a><\/p>\n

Repeat for both modules. You can follow the process at the bottom of the page:
\n\"ModuleImporting\"<\/a><\/p>\n

When everything is done, you should be able to use the module in Azure Automation. A simple native PowerShell script runbook that just lists some users would look like this:<\/p>\n

[PowerShell]
\n$AzureCred = Get-AutomationPSCredential -Name ‘AzureADCred’<\/p>\n

Connect-MsolService -Credential $AzureCred<\/p>\n

Get-MsolUser
\n[\/PowerShell]<\/p>\n

To give you an idea of how to assign a license:
\n[PowerShell]
\n$AzureCred = Get-AutomationPSCredential -Name ‘AzureADCred’<\/p>\n

Connect-MsolService -Credential $AzureCred<\/p>\n

$UserPrincipalName = ‘anders@mytenant.onmicrosoft.com’
\n$AccountSkuId = ‘mytenant:O365_BUSINESS_PREMIUM’<\/p>\n

$LicenseOptions = New-MsolLicenseOptions -AccountSkuId $AccountSkuId -DisabledPlans $null<\/p>\n

Set-MsolUserLicense -UserPrincipalName $UserPrincipalName -LicenseOptions $LicenseOptions -AddLicenses $AccountSkuId
\n[\/PowerShell]<\/p>\n

I haven’t tested the preview module fully in Azure Automation yet, but so far it seems to work fine (adding licenses and so on works!). Try it yourself and share your experiences!<\/p>\n

Happy automating Azure AD with Azure Automation \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"

Update: The Windows Azure Active Directory Module that was in preview when this was posted has been released and can be deployed straight to Azure Automation from this page: http:\/\/www.powershellgallery.com\/packages\/MSOnline\/1.0 The original post follows: The Azure AD PowerShell module have some dependencies that historically made it fail in Azure Automation. In fact, it’s the most […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false}}},"categories":[1171,111],"tags":[1201],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p3Zj0A-1Bn","_links":{"self":[{"href":"https:\/\/p0wershell.com\/index.php?rest_route=\/wp\/v2\/posts\/6161"}],"collection":[{"href":"https:\/\/p0wershell.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/p0wershell.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/p0wershell.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/p0wershell.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=6161"}],"version-history":[{"count":0,"href":"https:\/\/p0wershell.com\/index.php?rest_route=\/wp\/v2\/posts\/6161\/revisions"}],"wp:attachment":[{"href":"https:\/\/p0wershell.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=6161"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/p0wershell.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=6161"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/p0wershell.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=6161"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}