One of the tasks an Azure admin will probably have to do frequently when MFA is enabled for O365 users is to reset it. This can be achieved by manually use the “Require re-register MFA” option in the Azure admin portal. We at Provisior are all about automating as much
While working on a PowerShell script to add users in Azure AD recently, I walked into a situation you will sometimes have as a PowerShell scripter. You need to call some command, but given the input the parameters to supply differs. You could write a couple of “if this-input then
When you do a lot of automation at one point you will run into the situation that you need credentials for accessing some application or API. Obviously you don’t want to store those credentials somewhere in plain text. With PowerShell, one way to store sensitive data in a secure way
The other day I was working on some PowerShell scripts to manage shared mailboxes in O365. If you are familiar with this you obviously know that you need to setup a connection with Exchange online first. This will look something like this: $session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential
As I wrote about providing full insight in user access rights for cloud applications as well in one of my previous blogs, today I will start with a first example of this. We use Slack internally for quick communication between team members. Personally, I love Slack. You can quickly send
Today I learned a nice little trick one of our MSP partners uses in their PowerShell scripts. Provisior lets you define PowerShell parameters on a global level, so you can reuse them in different PowerShell templates you define. To do this, you link the parameters to the template and define
In September 2018 we released a version of Provisior in which we introduced a nice new feature: The ability to bind the output of a Powershell script as the source for a (multi-value) field in our dynamic Forms (link in Dutch only). This opened a whole new world for our
While setting up Provisior at a new customer we ran into an error while testing the on-boarding of a new user. The mailbox could not be enabled in the local Exchange 2013 server. The error Exchange returned was: Load balancing failed to find a valid mailbox database. Fortunately Google helped