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
Set Out of Office reply for users
One thing users tend to forget once in a while is activating the Out of Office reply in Outlook when they are going on a holiday leave. Obviously a situation you want to prevent as much as possible as it can lead to frustration by people sending a message and
Introduction on Member management
Although it’s introduced a couple of major releases ago, Member management is a powerful feature that some of our clients haven’t implemented yet. With Member management it’s possible to add and remove access in bulk to items in the service catalogue in a simple and fast way, without the need
Suppress import session output when connecting to O365
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
Current members: Slack
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
Hidden gem: Bulk approval of requests
One of our biggest goals is reducing the time necessary to complete requests as much as possible. By digitalizing workflows we’ve managed to do that very well. As our clients started using the workflows, edge cases appeared. Say you are a manager of multiple departments, it should be very common
Full insight in user access rights at all times
One of the key features of Provisior is to provide insight in user access rights. This used to be quite simple as most access rights where formed by Active Directory security groups for access to network shares, shared mailboxes, distribution lists and software applications. One of the primary use cases
Get all available PowerShell parameters by script
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
Send email in name of Provisior
By default Provisior will send emails to users in name of the actor. For instance, if a user requests access to a shared mailbox, and his/her department manager needs to approve this, the manager will receive an email in name of the user requesting. This is convenient, because the receiver
How to: Fill a Form field with the result of a REST api
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