Office 365 Administration with ScriptRunner

Author: | Reading time: 2 minutes | Category: Automation

O365 Administration mit PowerShell und ScriptRunner

This article has been translated automatically.

The use of Office 365 in companies is enjoying increasing popularity. With the significant spread and use of Office 365 services for user administration (Azure AD), messaging (Exchange Online and Skype for Business), collaboration (SharePoint Online) and other services such as Microsoft CRM, Microsoft ERP etc., the demands on administration are increasing enormously.

Microsoft pursues two basic strategies for the administration of Office 365 Services:

  • Point&Click administration via the web interface of Office 365, which is significantly reduced in scope and possibilities.
  • PowerShell Administration with scripts for automation. All possibilities are available here.

With the ScriptRunner version 2016R2 Corporate Suite the support for Office 365 administrators has been significantly extended. Fast automation and safe delegation are the focus of the innovations.

Office 365 Service Endpoints as a Target System

The administration of Office 365 using PowerShell is done through Service Endpoints. The service endpoints are addressed through appropriate PowerShell modules and connection configurations.

In ScriptRunner, Office 365 Service Endpoints can now be configured as target systems. Several service endpoints can also be combined in a target system. The settings in ScriptRunner Office 365 target systems combine both connection configuration and automatic handling with the appropriate PowerShell modules.

The advantage: Administrators do not have to worry about connection and PowerShell session handling for the Office 365 Services endpoints. The PowerShell scripts remain slim and purely use case oriented.

Version 2016R2 supports the following Office 365 services:

  • Office 365 Azure Active Directory for users, groups and service management
  • Exchange Online
  • SharePoint Online
  • Skype for Business Online

High security is guaranteed by the separation of rights known from ScriptRunner. You can assign administrative credentials to each service or service combination. You can then perform various actions with PowerShell scripts on the Endpoints service.

Customized Reporting

When actions are executed on an Office 365 Service endpoint, the results can be tracked in detail in a report. Information about both the Endpoint service and the administrative credential used is stored as part of the metadata.

Bulk actions at Office 365 multi-client services

Especially service providers manage and support the Office 365 clients of many clients. Many recurring tasks, such as regularly creating usage reports, comparing and adjusting configurations, etc., must be performed and automated for all these clients.

ScriptRunner also provides the ability to perform PowerShell actions on service endpoints in parallel on different Office 365 clients, such as reading and listing active users, assigned service licenses or mailbox usage, Sharepoint Site or library content, and so on.

With bulk actions, service providers can work much more efficiently and productively and also offer their customers a higher quality of service.

Requirements

To automate Office 365 with PowerShell, only a few steps are required:

  • Provision of the ScriptRunner Service Host
  • Installing the Office 365 PowerShell Modules on the Service Host
  • Creating the administrative credentials in ScriptRunner
  • Configuring the Office 365 Service Endpoints
  • Configuring actions for the corresponding use cases

For a quick start you can use theScriptRunnerAction Pack for Office 365 which we provide. It includes several scripts that you can use to immediately start automating or delegating your processes.

These posts might also be interesting for you:

Secure Password Server, PowerShell
ScriptRunner Server-Eye, Monitoring Automation, PowerShell Automation
Matrix42 und ScriptRunner, PowerShell Automation