---
title: Office 365 Provisioner
description: The PingFederate Office 365 Provisioner enables enterprises to provision users and groups to Office 365.
component: office365
page_id: office365:office_365_provisioner:pf_office365_connector
canonical_url: https://docs.pingidentity.com/integrations/office365/office_365_provisioner/pf_office365_connector.html
revdate: June 20, 2024
section_ids:
  features: Features
  intended-audience: Intended audience
  system-requirements: System requirements
---

# Office 365 Provisioner

The PingFederate Office 365 Provisioner enables enterprises to provision users and groups to Office 365.

The Office 365 Provisioner includes a quick connection template to easily set up a connection with Office 365, which can be used for single sign-on (SSO), provisioning, or both. The provisioner makes use of the Microsoft Graph API to communicate with Azure, which acts as the user and group repository for Office 365. The provisioner includes licensing support (`skuId` and `disabledPlans` attributes) and the ability for managers to be assigned to provisioned users (`manager` and `pingSourceDN` attributes).

|   |                                                                                                            |
| - | ---------------------------------------------------------------------------------------------------------- |
|   | This provisioner is for outbound provisioning only and is not intended for inbound or hybrid environments. |

## Features

* Browser-based SP and IdP-initiated SSO

* Includes support for user and group life cycle management (including creates, updates, disables, and deletes).

* Includes configuration options for workflow capabilities (for example, the ability to disable updates).

## Intended audience

This document is intended for PingFederate administrators.

If you need help during the setup process, see the following resources:

* The following Knowledge Base article:

  * [PingFederate Office 365 FAQ](https://support.pingidentity.com/s/article/PingFederate-Office-365-FAQ)

* The following sections of the PingFederate documentation:

  * [Identity provider SSO configuration](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/pf_ident_provid_sso_config.html)

  * [SP connection management](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/pf_sp_connect_management.html)

  * [Managing digital signing certificates and decryption keys](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/help_certmanagementtasklet_dsigsigningcert_certmanagementstate.html)

  * [Datastores](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/pf_datastores.html)

  * [Configuring outbound provisioning](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/help_spconnectionconfigtasklet_saasprovisioningstate.html)

  * [Configuring outbound provisioning settings](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/help_protocolsettingstasklet_saasglobalprovisioningsettingsstate.html)

## System requirements

* PingFederate 9.0 or later.

* An existing Office 365 account.

* SSO requires the following:

  * A domain that has been created for use as a federated domain and is accessible and DNS resolvable by Microsoft.

  * Administrative access to modify DNS records for the federated domain.

  * The PingFederate server must be externally accessible.

  * A Windows platform in order to run SSO related configuration using Powershell. The Windows platform must be able to access the Azure management portal.