Scoping Outlook Add-in users in the Microsoft 365 admin center

Overview

This article covers how to deploy the Opensense Outlook Add-in to users in your Microsoft 365 organization, manage the group scope, and grant admin consent so users don’t get permission prompts one by one.

Before you deploy, confirm that your organization meets the requirements in Outlook Add-in supported environments. Test with a pilot group before you roll out to the entire organization.

GCC High

Microsoft’s Integrated apps portal isn’t available in government clouds. For GCC High, see Opensense Outlook Add-in integration with GCC High environments.

Step 1: Set the deployment scope

1. Sign in to the Microsoft 365 admin center.
2. Go to Settings > Integrated apps.
3. Find and select Opensense Email Signatures in the list.
4. Select the Users tab, or Edit users, and choose who gets the add-in:
   • Entire organization: every user gets the add-in. Use this only if all outbound email should get an Opensense signature.
   • Specific users/groups: only the users and groups you pick. Make sure every user who needs the add-in is in the assigned group.
   • Just me: only you, the administrator. Use this for initial testing only.
5. Select Update to save your changes.

Nested groups aren’t supported

Microsoft doesn’t support nested groups for Centralized Deployment. Users must be assigned directly to a top-level Microsoft 365 group. Integrated apps also doesn’t support dynamic distribution groups or non-mail-enabled security groups. For details, see Microsoft’s Centralized Deployment FAQ.

Step 2: Add users to the scoped group

If the add-in is deployed to Specific users/groups, make sure everyone who should get it is a member of the assigned group.

1. In the Microsoft 365 admin center, go to Teams & groups > Active teams & groups.
2. Select the group assigned to the Opensense Add-in (for example, opensense_addin@yourdomain.com).
3. On the Membership tab, select Members, and then select Add members.
4. Search for and select the users who should get the Opensense Add-in.
5. Select Save.

To remove a user instead, open the same group, and on the Membership tab, select Members. Select the X next to the user, and then select Save. Users removed from the group stop getting Opensense signatures after about 48 to 72 hours. To remove the add-in itself, see Removing the Outlook Add-in in the Microsoft 365 admin center.

Add-in never appeared for one user?

If a user’s add-in never appeared, or their profile seems stuck, remove that user from the group and add them again. This resets their deployment queue without affecting anyone else. See Step 7 in Troubleshooting the Outlook Add-in.

Step 3: Re-grant admin consent

Without admin consent, each user is prompted to accept permissions when the add-in deploys. Grant admin consent in advance, so the add-in activates without any user action.

1. Sign in to the Microsoft Entra admin center.
2. Go to Entra ID > Enterprise apps > All applications.
3. Search for and select Opensense Email Signatures.
4. Under Security, select Permissions.
5. Select Grant admin consent for [Your Organization].
6. Confirm the consent to allow the required permissions.

You can also do this in the Azure portal, under Microsoft Entra ID (formerly Azure Active Directory) > Enterprise applications.

Re-grant after every scope change

Re-grant admin consent any time you add users or groups to the deployment scope. Changes can take up to 72 hours to fully propagate. Restarting Outlook can speed this up for individual users.

What’s next

• Outlook Add-in overview
• Removing the Outlook Add-in in the Microsoft 365 admin center
• Configuring the Outlook Add-in in Domain Settings
• Troubleshooting the Outlook Add-in