Roll out Online Meeting Link to a user group

Deutsch | Online Meeting Link

Use this procedure to automatically install the Online Meeting Link personal app and pin it in the Teams app bar for one group. It does not add channel tabs or create teams. Leave Global (Org-wide default) unchanged.

Prepare the audience

1. Complete installation, API approval, and Teams synchronization.
2. Create or select a supported user group, for example an Entra security group named OnlineMeeting-Users. Start with a small pilot membership.
3. Record existing app availability, installation assignments, and setup policies. Choose an in-group account and an out-of-group account for verification.
4. In Teams admin center > Teams apps > Manage apps, verify the app’s identity and that it supports personal installation. If installation is unavailable for the deployed app, investigate its package/scopes before continuing; pinning alone is not proof of successful automatic installation.

Distinguish three controls:

• Availability: who may discover/use the app.
• Installation: whose personal Teams client receives the app automatically.
• Pinning: whose effective setup policy places the app in the app bar.

Assigning installation to a group does not, by itself, remove existing access or installations for everyone outside the group.

1. Configure automatic installation

Use the path available in your tenant. Do not configure both paths blindly.

App-centric management

1. Open Online Meeting Link under Teams apps > Manage apps.
2. Select Edit installs, or open Users and groups > Installs > Install app in the app details.
3. Choose the option for specific users/groups and select OnlineMeeting-Users. Do not select everyone. Review existing assignments before changing them.
4. Select Apply and verify that the intended group is listed.

This installation flow also makes the app available to the selected audience. Review availability separately if access must be restricted to that group: under the app’s availability controls, use Specific users or groups rather than Everyone, retaining any other explicitly approved audiences. Changing availability is an access decision, not a necessary consequence of installing the app for one group.

Legacy setup-policy installation

Only use this path if your tenant still supports editing installed apps in setup policies. After migration, these controls can be read-only for additions; use app-centric installation instead.

1. Ensure the app is allowed for the target users through the applicable app permission controls.
2. Create a custom app setup policy named OnlineMeeting-Users, preserving the installed apps and settings that the audience already needs.
3. Under Installed apps, choose Add apps, select Online Meeting Link, and save.
4. Use this same policy for pinning and group assignment below.

2. Configure app-bar pinning

1. Open Teams apps > Setup policies.
2. Create a custom policy named OnlineMeeting-Users, or edit the dedicated policy created in the legacy installation path.
3. Preserve other required apps, their order, and relevant settings. A custom policy is not an additive overlay on the global policy.
4. Under Pinned apps, add Online Meeting Link and choose its position.
5. Save the policy. Do not modify Global (Org-wide default).

Pinning is separate from the installation assignment in app-centric tenants. If the app cannot be selected, check its availability and supported scope.

3. Assign the setup policy to the group

1. In Setup policies, open Group policy assignment.
2. Add an assignment for OnlineMeeting-Users, select the dedicated app setup policy, and choose the appropriate rank relative to existing group assignments.
3. Save and inspect the effective app setup policy for a pilot user.

A direct user assignment takes precedence over a group assignment. Where multiple groups assign the same policy type, group assignment ranking decides which applies. The global policy is the fallback. Resolve conflicts through your normal change process rather than removing unrelated assignments.

Group and policy changes propagate asynchronously. Do not promise immediate installation or pinning, or treat a client refresh as proof that propagation has completed.

4. Verify the rollout

For the in-group user, verify the effective setup policy, open the personal app in Teams web and desktop, and create a real test meeting. Check join-link copying and, if supported/configured, the expected branding. A working channel tab is not a substitute for testing the personal app.

If results differ, check group membership, direct policy assignments, group ranking, installation assignments, app availability, and propagation before changing the package. Meeting creation failures also require the API/license/ policy checks in the installation guide.

Undo the scoped rollout

Record the previous state before making changes. Remove only this group’s installation assignment (or its entry in the dedicated legacy policy) and remove/replace the group’s dedicated setup-policy assignment. Check which policy becomes effective afterward.

Removing an assignment does not guarantee that an already installed app is uninstalled. Verify installed state and use the supported uninstall controls in your tenant/client if removal is required. Review app availability separately if access must be revoked. Do not delete the tenant package, change global policy, or revoke shared Graph grants to undo a group rollout.

Microsoft Learn

• Preinstall Teams apps
• App-centric availability management
• App setup policies and pinning
• Assign policies to users and groups
• Policy precedence