Install Online Meeting Link

Deutsch | Online Meeting Link

This guide distributes Online Meeting Link as a custom application through your organization’s catalogs, sometimes called sideloading. It does not publish the app to the public Teams store and does not require developer debug manifests.

Prerequisites

• A Microsoft 365 tenant with SharePoint Online, Teams, and a tenant app catalog.
• Access to upload and deploy packages in that tenant app catalog, plus Teams administration rights to manage the app and its rollout.
• An administrator authorized to approve Microsoft Graph permissions through SharePoint API access. For Microsoft Graph approval, use a Global Administrator; SharePoint administration alone is not sufficient.
• Test users with access to SharePoint and Teams, the required licenses, and permission to create Teams meetings under your organization’s policies.
• A reviewed release package. The current source uses SPFx 1.24.1; complete acceptance testing in your own tenant before production deployment.

Ask the release owner to complete the developer name, website, privacy URL, and terms-of-use URL in the solution configuration before packaging. These fields are currently empty in the source.

1. Obtain the package

The production build in src/spfx-kyanis-onlinemeeting uses npm run build. Its output, relative to that directory, is:

  sharepoint/solution/spfx-kyanis-onlinemeeting.sppkg
  

Use the released .sppkg, not a source archive or the legacy application’s package. The solution ID is 1f482fa7-0e09-413d-8dda-e741d014f3fc. The component ID is 4bd25887-288a-414d-a098-ef9b0d051779. Keep a copy of the last approved package and record the version being deployed.

2. Upload and deploy tenant-wide

1. Open the SharePoint admin center, then More features > Apps, and open the tenant app catalog/manage apps experience.
2. Upload spfx-kyanis-onlinemeeting.sppkg. In the classic catalog, use Apps for SharePoint. For an update, confirm the existing solution ID before replacing the package.
3. Review the trust/deployment dialog and requested access.
4. Select the option to make the solution available to all sites in the organization, then confirm Deploy or Enable app, as offered by the catalog experience.
5. Verify that deployment completed without errors.

Online Meeting Link sets skipFeatureDeployment: true, enabling this tenant-wide option, and includes its client-side assets in the solution package. You do not need to add the app separately to every site. Tenant-wide availability does not add the web part to pages, install the Teams app, or approve Graph access.

3. Approve Microsoft Graph access

1. In the SharePoint admin center, open Advanced > API access.
2. Review the pending request for resource Microsoft Graph, scope OnlineMeetings.ReadWrite, associated with this deployment.
3. Have the authorized administrator approve the request after security review. If the scope is already approved, verify the existing approval instead.
4. Confirm that the permission appears in the approved list.

This is delegated access through SPFx: Online Meeting Link creates meetings as the signed-in user using POST /me/onlineMeetings. Do not substitute application permissions, add a client secret, or create a separate app registration for these instructions. SPFx API grants are shared by SPFx solutions in the tenant; do not treat this approval as an isolated per-app security boundary. Approval does not override user licenses, meeting policies, or access controls.

4. Check SharePoint

1. Edit a modern SharePoint page using an account allowed to edit that page.
2. Add Online Meeting Link (or Teams-Besprechung) from the web part picker, and publish the page.
3. Open it as a test user. Enter a subject and valid start/end times.
4. Create one meeting, check the join information, and copy it into the intended target application. Confirm that the join link opens.

The app does not send invitations or create an Outlook calendar entry. Full-page hosting is also declared as supported; test it if your deployment uses that experience.

5. Publish the app to Teams

1. In the tenant app catalog, select the deployed Online Meeting Link solution.
2. Choose Add to Teams or Sync to Teams. The label differs between catalog experiences.
3. Wait for confirmation. SharePoint publishes the developer-provided TeamsSPFxApp.zip included in the solution to the organization’s Teams catalog. The package contains English and German app descriptions.
4. Open Teams admin center > Teams apps > Manage apps. Locate the correct app and verify its identity, status, and availability for your test users. Apply your organization’s app review and access rules.
5. In Teams, add the app from your organization’s app catalog as a test user. Test the personal app. The current package does not declare a channel or meeting tab.

Catalog publication is not automatic installation. For a selected audience, continue with group installation and pinning. For branding, see Teams customization.

Acceptance checks and troubleshooting

Perform these checks in the target tenant; a local preview is not a substitute.

Verify English and German UI, the hosts you use, Teams light/dark/high-contrast themes, and copying in Teams desktop and web. Record the account, package version, client, error, and outcome without collecting meeting details unnecessarily.

Updates and rollback

For a reviewed update, keep the solution/component identities stable, use an appropriately versioned package, replace and deploy it in the same catalog, review any new permission requests, sync to Teams again, and repeat acceptance checks. Recheck branding and group assignments after synchronization.

If an update fails, stop further rollout and have the release owner prepare a correctly versioned rollback package from the last approved source. Do not assume uploading a lower version is supported. Redeploy, resync, and retest. Do not delete the solution or revoke shared SPFx API grants as a quick rollback.

Microsoft Learn

• Tenant-wide SPFx deployment
• SharePoint API access and required administrator roles
• SPFx permission requests and approval
• Deploying SPFx solutions to Teams