Teams Manager utilizes user accounts to perform certain API actions in the name of the signed-in user (delegated permissions). For example, this is the case when it comes to reading out data from Template Teams and creating new Teams (Provisioning).

In general, Teams Manager can read out and provision data in two distinct ways.

When Teams Manager provisions a new Team based on a Template Team, the Template Team's data has to be read out via the API in the name of the user who is Approving/Creating the Team.

In order to make that happen, the respective user (Approver/Team-Creator) has to be added to the Template Team temporarily, in order to read out the necessary data. Afterwards, that user is automatically removed again.

This approach is necessary on a technical level; however, it comes with one slightly annoying side effect: Whenever a user is added to the Template Team, they receive a notification email from Microsoft. As you might guess, depending on the number of Teams that you Approve/Create throughout the day, the number of emails you'll receive can become overwhelming.

We've already explored a workaround that allows you to stop receiving these emails here

However, there is also another Option:
​

If you've specified a Service Account during installation, instead of impersonating the Approver/ Requester, Teams Manager can utilize this Service Account instead.

Here's how it's done:

Now all Teams will be provisioned in the name of the Service Account you've attached.

Get further assistance with Teams Manager through our support chat widget within the app, or reach out to us at [email protected]