New versions of the WAAD and the AADRM modules are available

Seems Microsoft decided to skip the announcements on these two. You can get the new version of the WAAD module from the links at this article. ​For the AADRM module, go here.

I’m still going over the list of the new things in the WAAD module, but it doesn’t seem like much has changed. We have some new cmdlets:

  • Confirm-MsolEmailVerifiedDomain (use to claim ownership of Azure AD tenant, see
  • Get-MsolDirSyncProvisioningError (supposedly will give the same info as the emails with dirsync errors, but doesn’t seem to be working currently)

We also have some new parameters for the Get-MsolUser cmdlet:

  • DirSyncProvisioningErrors (shows empty for all users)
  • IndirectLicenseErrors (again empty for all users)
  • AlternativeSecurityIds (empty for all users, maybe hint on allowing Microsoft IDs with Office 365?)
  • ServiceInformation (seems to contain some information specific to the Social listening licenses. All Global Admins in the tenant have the parameter configured. This is the info it contains:
PS C:\> (Get-MsolUser).ServiceInformation.ServiceElements.ServiceParameters.ServiceParameter

Name                                                                                      Value
----                                                                                      -----

It’s a bit disappointing that parameters like UserLandingPageIdentifierForO365Shell or UserThemeIdentifierForO365Shell are still not editable even with the new version of WAAD.

A much welcome addition to the AADRM module is the ability to add custom templates. To create a new custom template, you can use the Add-AadrmTemplate cmdlet. And you can also import your AD RMS templates using the Import-AadrmTemplate cmdlet. To publish a template, you can use the Set-AadrmTemplateProperty cmdlet:

Set-AadrmTemplateProperty -TemplateID 28168524-29c3-44f1-9e11-ea6c60bb6428 –Status Published

Update 30/09/2014: Seems I’ve missed an important change, we now have the WhenCreated attribute for WAAD objects!!! This is easily one of the most requested features, so it’s much welcome even in it’s current buggy state (it doesnt populate the attribute values if you use the -All switch for Get-MsolUser or use the cmdlet without specifying a searchstring or UserPrincipalName. Until this is fixed, you can use the following cmdlet instead:

 Get-MsolUser | ft Userp*,@{n="WhenCreated";e={(Get-MsolUser -UserPrincipalName $_.userprincipalname).WhenCreated }})

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.