Enable Microsoft Teams integration in the Time package
You'll use the Enable MS Teams Integration feature toggle to turn on Microsoft Teams integration for your Sage People organization.
Install the 'Sage People Employee Self Service Integration (Prod)' External Client App
End users will be unable to authenticate unless they've installed this package.
To obtain or install the package, contact the Customer Success team. They can provide the package details or complete the installation for you.
Verify the installation
-
Go to Setup.
-
Go to External Client App Manager.
-
Check you can see the app listed as Sage People Collaboration Production.
Enable Microsoft Teams integration
-
Go to Setup and select Apps.
Select Packaging and then Installed Packages.
-
Find the Sage People Time package and select Configure.
-
Under Time Features, find the Enable MS Teams Integration setting. Set this to On.
Setting What it does On Enables the integration for the organization. Off Disables integration for the organization. Sandbox Enables integration for the organization's Sandbox orgs only. Doesn't affect production orgs. - Set the MS Teams Daily Rundown Scheduled Time.
This setting determines the time of day when the system sends the manager's daily information message ("Today's rundown").
To disable the daily rundown, select Not Active.

-
Set the MS SSO Registration Scheduled Time.
This setting determines the time of day. Then, the system synchronizes active team members you assigned to the Teams integration with the single sign-on service for Microsoft 365.
This ensures users can sign in to your organization's Sage People instance through Microsoft Teams using single sign-on.
To disable SSO registration for Teams, select Not Active. If you disable this, users need to configure your organization's custom domain manually. They'll do this when first signing in through Microsoft Teams.
- Select Save.
If you're also using Outlook calendar integration, you can also enable Calendar integration on this screen. You can use this to add approved absences to team members' and managers' Calendars. Calendar integration requires extra setup. See Calendar integration: introduction.
OAuth Policy Settings
The Sage People Collaboration Production external client app uses the following default OAuth configuration:
| Option | Default Setting |
|---|---|
| IP Relaxation | Enforce IP restrictions |
| Refresh Token Policy | Expire refresh token after a specific time |
| Refresh Token Validity | 365 Days |
| High assurance session required | No |
| Session Timeout (Minutes) | None (uses profile/org session timeout) |
Session Timeout Behavior:
Salesforce determines the session timeout using the value you defined in the user’s Profile.
If the Profile doesn't specify a timeout, Salesforce uses the org-wide timeout it defines under Session Settings (typically two hours).
IP relaxation settings
By default, the app enforces any IP restrictions in place for Sage People. If you use IP restrictions on profiles, you can still allow users to use the Teams app. This includes when they aren’t on your list of approved IPs. You can adjust this setting via the app manager.
-
Go to Setup and select External Client App Manager.
-
Select the Sage People Collaboration Prod external client app.
-
Under Policies, click Edit.
-
In OAuth policies, change the IP relaxation settings.
Fully relaxing the IP restrictions allows you to use the app from any IP. There are two options in between which you can read more about here: Connected App IP Relaxation and Continuous IP Enforcement.
Updating the Refresh Token Policy (If required)
You can adjust the Refresh Token Policy to require users to re-authenticate periodically to Sage People within Microsoft Teams.
-
Go to Setup and select External Client App Manager.
-
Select the Sage People Collaboration Prod external client app.
-
Under Policies, click Edit.
-
In the App Authorization section, update the Refresh Token Policy as you need.
-
Click Save.
For further details about managing external client apps, see the Salesforce help article Manage External client App.
Known issues when migrating from a previously connected app (Digital Assistant Prod)
You can notice changes during the transition if you've used the Microsoft Teams integration before and you authenticated with the old connected app. (Known as Digital Assistant Prod). You can expect the following behavior when moving to the new Sage People Collaboration Prod external client app:
-
Session Expired - User Re-Authenticates Normally
If your login session expires, any actions in Microsoft Teams prompt a login request. The system redirects you to authenticate using the new external client app. You won't observe any change in behavior. Microsoft Teams integration will continue to function normally after re-authentication -
Session Active - No Immediate Impact
If your current session is still active, all Microsoft Teams actions continue to work without interruption. Once your session eventually expires, the system prompts you to log in and will then authenticate via the new external client app -
Session Active but Encounters Errors
If your session is active and you attempt an action in Microsoft Teams, you can see the following errors: "Session expired or invalid". Or, when attempting to log in again, "You are already logged in". To resolve this, log out of the integration and log back in again
