Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The PagerDuty Schedules Microsoft 365 Copilot connector integrates PagerDuty schedule data into Microsoft 365, enabling Copilot and Microsoft Search to surface schedule information directly within apps like Teams, Outlook, and SharePoint.
This article provides information about the configuration steps that PagerDuty admins need to complete in order for your organization to deploy the PagerDuty Schedules connector.
For information about how to deploy the connector, see Deploy the PagerDuty Schedules connector.
Setup checklist
The following checklist lists the steps involved in configuring the PagerDuty environment and setting up the connector prerequisites.
Configure the PagerDuty environment
| Task | Role |
|---|---|
| Identify the PagerDuty service region | PagerDuty admin |
| Enable Developer Mode in PagerDuty | PagerDuty admin |
Set up OAuth prerequisites
| Task | Role |
|---|---|
| Register an OAuth 2.0 app in PagerDuty | PagerDuty admin |
| Configure redirect URLs | PagerDuty admin |
| Configure OAuth scopes | PagerDuty admin |
| Obtain Client ID and Client Secret | PagerDuty admin |
Configure the PagerDuty environment
The following sections describe the admin tasks to configure the PagerDuty environment to enable and optimize the connection.
Identify the PagerDuty service region
PagerDuty allows customers to choose the geographic service region of the PagerDuty data centers that host their account. The REST API URL varies depending on your service region:
- US service region:
https://api.pagerduty.com - EU service region:
https://api.eu.pagerduty.com
To identify your PagerDuty service region:
- Sign in to your PagerDuty account.
- Review the URL in your browser address bar:
- For the US region, your URL typically appears as
https://[your-subdomain].pagerduty.com - For the EU region, your URL typically appears as
https://[your-subdomain].eu.pagerduty.com
- For the US region, your URL typically appears as
Make note of your REST API URL as you'll need it when deploying the connector in the Microsoft 365 admin center.
For more information, see Service regions in the PagerDuty documentation.
Enable Developer Mode in PagerDuty
To register OAuth apps in PagerDuty, you must first enable Developer Mode.
To enable Developer Mode:
- Sign in to your PagerDuty account with administrator permissions.
- Navigate to Integrations > Developer Mode.
- If Developer Mode is not already enabled, choose Enable Developer Mode.
Note
You must be a PagerDuty account administrator to enable Developer Mode. If you don't see this option, contact your PagerDuty account owner.
Set up OAuth prerequisites
The following sections describe the prerequisite steps to complete before you deploy the PagerDuty Schedules connector.
Register an OAuth 2.0 app in PagerDuty
The PagerDuty Schedules connector uses OAuth 2.0 for authentication. You must register an OAuth app in PagerDuty to obtain the client credentials required for connector authentication.
To register an OAuth 2.0 app:
Sign in to your PagerDuty account with administrator permissions.
Go to Integrations > Developer Mode.
Select Create New App.
In the app registration form, enter the following information:
- App Name: Enter a descriptive name such as "Microsoft 365 Copilot Connector"
- Description: Enter a description such as "OAuth app for Microsoft 365 Copilot connector integration"
- Category: Select Integration
Select Scoped OAuth as the OAuth type.
Important
You must select Scoped OAuth to ensure proper authentication. Standard OAuth is not supported by the connector.
Continue to configure the redirect URLs and OAuth scopes as described in the following sections.
For more information about OAuth functionality in PagerDuty, see OAuth Functionality and Register an App in the PagerDuty developer documentation.
Configure redirect URLs
OAuth 2.0 authentication requires redirect URLs (also called callback URLs) to complete the authorization flow. The redirect URL varies based on your Microsoft 365 environment.
In your PagerDuty OAuth app settings, add the appropriate redirect URL for your environment:
- For Microsoft 365 Enterprise:
https://gcs.office.com/v1.0/admin/oauth/callback - For Microsoft 365 Government:
https://gcsgcc.office.com/v1.0/admin/oauth/callback
Important
Make sure that you use the correct redirect URL for your environment. Using an incorrect redirect URL prevents the OAuth authorization flow from completing successfully.
Configure OAuth scopes
The PagerDuty Schedules connector requires specific OAuth scopes to access schedule data and enforce permissions. In your OAuth app settings in PagerDuty, select the following scopes:
| Scope | Access level | Description |
|---|---|---|
| Audit records | Read Access | Required to access audit log information for schedules. |
| Schedules | Read Access | Required to read schedule data including on-call rotations and coverage information. |
| Teams | Read Access | Required when Advanced Permissions is enabled to enforce team-based access controls. |
| Users | Read Access | Required to map PagerDuty users to Microsoft 365 identities for permission enforcement. |
Note
The connector requires read-only access. It doesn't require write or delete permissions.
To configure OAuth scopes:
- In your PagerDuty OAuth app settings, scroll to the OAuth Scopes section.
- Select the checkbox next to each required scope:
- Audit records – Read Access
- Schedules – Read Access
- Teams – Read Access
- Users – Read Access
- Review the selected scopes to ensure all required permissions are enabled.
Obtain Client ID and Client Secret
After configuring your OAuth app, you need to obtain the Client ID and Client Secret that you'll use to authenticate the connector during deployment.
To obtain your Client ID and Client Secret:
- In your PagerDuty OAuth app settings, choose Save to save your app configuration.
- After saving, the Client ID appears in the app details section. Copy this value.
- Choose Generate Client Secret or Show Client Secret (depending on whether a secret already exists).
- Copy the Client Secret value.
Important
Store the Client ID and Client Secret securely. You'll need these credentials when deploying the connector in the Microsoft 365 admin center. The Client Secret is shown only once. If you lose it, you'll need to generate a new secret.