---
title: "Outlook Add-in: Scope Users via Microsoft 365 Admin"
slug: "clone-outlook-add-in-scope-users-for-opensense-in-m365-admin"
description: "Step-by-step instructions for deploying the Opensense Outlook Add-in via Microsoft 365 Centralized Deployment, including setting deployment scope, managing group membership, and granting admin consent."
updated: 2026-03-20T18:08:38Z
published: 2026-03-20T18:08:38Z
canonical: "help.opensense.com/clone-outlook-add-in-scope-users-for-opensense-in-m365-admin"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.opensense.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Outlook Add-in: Scope Users via Microsoft 365 Admin

## Overview

This article covers how to deploy the Opensense Outlook Add-in to users in your Microsoft 365 organization, manage group scope, and grant admin consent to prevent per-user permission prompts.

Before deploying, confirm your organization meets the requirements in [Supported Environments for the Opensense Outlook Add-in](https://help.opensense.com/docs/supported-environments-for-the-opensense-outlook-add-in). Test with a pilot group before rolling out to the entire organization.

## Step 1: Set the deployment scope

1. Sign in to the [Microsoft 365 Admin Center](https://admin.microsoft.com).
2. Navigate to **Settings > Integrated Apps**.
3. Locate and select **Opensense Email Signatures** from the list.
4. Review and set the deployment scope:
  - **Entire Organization** — applies the add-in to all users. Use only if all outbound emails should receive an Opensense signature.
  - **Specific Users/Groups** — targets specific individuals or groups. Ensure all required users are included in the assigned group.
  - **Just Me** — applies only to the administrator. Use for initial testing only.
5. Click **Update** to save changes.

> [!NOTE]
> Microsoft does not support nested groups for Centralized Deployment. Users must be directly assigned to a top-level Microsoft 365 group. See [Microsoft's Centralized Deployment FAQ](https://learn.microsoft.com/en-us/microsoft-365/admin/manage/centralized-deployment-faq?view=o365-worldwide) for details.

## Step 2: Add users to the scoped group

If the add-in is deployed to Specific Users/Groups, ensure all intended users are members of the assigned group.

1. In the Microsoft 365 Admin Center, navigate to **Groups > Active Groups**.
2. Locate the group assigned to the Opensense Add-in (for example: `opensense_addin@yourdomain.com`).
3. Click **Members**, then select **Add Members**.
4. Search for and select the users who should receive the Opensense Add-in.
5. Click **Save** to confirm changes.

If users are removed from the group, they will stop receiving Opensense signatures after approximately 48 to 72 hours.

## Step 3: Re-grant admin consent

Without admin consent, end users will be prompted to accept permissions individually when the add-in deploys. Granting admin consent in advance prevents this and ensures the add-in activates without requiring user action.

1. Sign in to the [Azure Portal](https://portal.azure.com).
2. Navigate to **Azure Active Directory > Enterprise Applications**.
3. Search for and select **Opensense Email Signatures**.
4. Under **Security**, select **Permissions**.
5. Click **Grant Admin Consent for [Your Organization]**.
6. Confirm the consent to allow the required permissions.

Admin consent should be re-granted any time new users or groups are added to the deployment scope. Changes can take up to 72 hours to fully propagate. Restarting Outlook can help expedite the process for individual users.

## Related articles

- [Outlook Add-in Overview](https://help.opensense.com/docs/outlook-add-in-overview-1)
- [Supported Environments for the Opensense Outlook Add-in](https://help.opensense.com/docs/supported-environments-for-the-opensense-outlook-add-in)
- [Outlook Add-in Domain Settings with Scenarios and Best Practices](https://help.opensense.com/docs/clone-outlook-add-in-domain-settings-with-scenarios-and-best-practices)
- [Outlook Add-in Troubleshooting Guide](https://help.opensense.com/docs/clone-outlook-add-in-troubleshooting-guide)