If you use Azure Runbooks, but develop scripts locally first…you may like to display progress indicators to yourself when handling large amounts of records / data with Write-Progress.
Be sure to parameterise this, because if you use Write-Progress in an Azure Runbook, it will seriously slow your runbook down, increasing the cost, and if there are over 4000 write-progress calls the runbook will hang and crash.
This just made my day, as working with Azure AD through CSP
is was a pain in the ass. Microsoft finally enabled Azure AD management through the new Azure AD Portal!
As a guy who really likes to script things, I was very happy to read this today:
Firstly, my Powershell scripts / sessions can now be secured using MFA, without having to rewrite my scripts, except those where I built the Credential object with preset credentials….but that’s old anyway.
Secondly, I can now finally manage Registered Devices with the same Module, allowing me to use these commands:
You can use either the owner’s UPN or the device ID with these commands.
Now isn’t this awesome?
Azure finally announces full support for all services that use Domain Controllers, natively! No more building your domain controllers on VM’s in Azure, it’s become an actual service with these (and more) features:
- Native support (works like a real domain controller) for all protocols (kerberos, ntlm, ldap)
- Group policies
- Domain joins for devices
- Compatible with and linked to Azure AD
- Priced per hour
If you have your own domain, don’t forget to set up AADConnect with password sync enabled.
And this is a bit inconvenient, but if you’re running on Azure AD only, you’ll have to expire the passwords of all your users first.
But still, a much requested and anticipated feature we can finally start playing with!