Skip to content

W-23907421-teams-GA-fa #547

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
failup merged 2 commits into from
Aug 21, 2026
Merged

W-23907421-teams-GA-fa #547

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ef13142
W-23907421-teams-GA-fa
failup Aug 18, 2026
a54e67a
Update exp-teams-integrate.adoc
failup Aug 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
81 changes: 79 additions & 2 deletions modules/ROOT/pages/exp-teams-integrate.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,15 @@ Install the MuleSoft for Teams app in your Microsoft Teams tenant to interact wi

NOTE: This tool uses generative AI, which can produce inaccurate or harmful responses. Review for accuracy and safety before using.

[[before-you-begin]]
== Before You Begin

Before setting up the Teams integration, verify that the following requirements are met:

* *Agentforce Enabled*: Agentforce must be enabled within your Anypoint Platform organization.
* *Salesforce-Anypoint Connection*: Your Anypoint Platform organization must be fully connected to your Salesforce organization.
* *Early Access Program*: The MuleSoft Agent feature must be enabled for your organization by the MuleSoft team as part of the Early Access Program. Contact your Customer Success Manager (CSM) or Account Executive (AE) to join the program.

[[connect-teams-tenant]]
== Connect Your Microsoft Teams Tenant to the MuleSoft Organization

Expand All @@ -32,10 +41,19 @@ The app requests the following permissions:
. After the installation completes, the confirmation page displays *Microsoft Teams integration installed*. Click *Back to Settings*.
+
In *Notifications* > *Settings*, the *Microsoft Teams Setup* section now shows *Installed* and displays the bound tenant ID.
. Click *Grant Access* to allow the app to browse your Teams directory for channel and team member access.
. In Microsoft Teams, review the permissions requested and click *Accept*.
+
After access is granted, configure notification channels in the *Notification Channels* section.

After installation, the MuleSoft Agent app appears in Microsoft Teams Admin Center under *Manage apps* as available to everyone and unblocked.

To disconnect the integration, click *Disconnect* in the *Microsoft Teams Setup* section.
To disconnect the integration:

. Click *Disconnect* in the *Microsoft Teams Setup* section.
. Confirm the disconnection. This immediately revokes MuleSoft's access to your Teams tenant and stops all notifications.
+
The MuleSoft app remains in the Microsoft Teams Admin Center. To fully remove it, a Teams administrator must uninstall it from the Admin Center, or right-click the app in Teams and select *Uninstall*.

[[begin-using-agent]]
== Begin Using the MuleSoft Agent
Expand Down Expand Up @@ -66,7 +84,8 @@ To start using the agent in Teams:
. Under *Built for your organisation*, find *MuleSoft Agent* and click *Add*.
. Click *Open* or select a channel where you want to use the app.
. The agent sends a welcome message. Select a prompt suggestion or type a message to start.
. If prompted, click *Connect to Anypoint* and sign in with your Anypoint Platform credentials.
. If prompted, click *Connect to MuleSoft* and sign in with your Anypoint Platform credentials.
. After authenticating, close the browser tab to complete account linking. Return to Teams to continue the conversation.

After you authenticate, you can use the agent to list APIs, agents, MCP servers, view governance reports, and more.

Expand Down Expand Up @@ -98,6 +117,64 @@ You can use the MuleSoft Agent to perform these platform tasks in Teams:
* *Run governance, monitoring, and cost drill-ins*: Generate governance, monitoring, and cost reports on request.
* *Take governance actions*: Apply policies and apply cost management recommendations.

[[microsoft-graph-permissions]]
== Microsoft Graph Permissions

The MuleSoft for Microsoft Teams app requires the following Microsoft Graph permissions. Use this information when your security or IT team asks for justification before approving the app installation.

[cols="2,1,3", options="header"]
|===
|Permission |Type |Purpose

|`AppCatalog.Read.All`
|Application
|Verifies that the MuleSoft app is properly published in your Teams app catalog. Without this, the app cannot confirm its own availability, and users see silent failures instead of actionable setup errors.

|`AppCatalog.ReadWrite.All`
|Delegated
|Required when a Teams admin publishes or updates the MuleSoft app package in your catalog. Only exercised during install or upgrade — not at runtime — and scoped to the consenting admin's session.

|`AppCatalog.ReadWrite.All`
|Application
|Allows the MuleSoft app to receive updates, such as new Adaptive Card formats or capability additions, without requiring an admin to manually republish each time.

|`Channel.ReadBasic.All`
|Application
|Delivers API alerts and deployment notifications to specific channels you configure. The app reads channel names and IDs to resolve routing rules. It reads channel metadata only — not message content.

|`Team.ReadBasic.All`
|Application
|During setup, lets you map MuleSoft environments and business groups to specific teams without manually looking up team IDs. Read-only access to team names and descriptions — no access to members or content.

|`TeamsAppInstallation.ReadWriteAndConsentForTeam.All`
|Application
|Lets a Teams admin roll the app out to all relevant teams in a single action with automatic RSC consent, rather than requiring each individual team owner to install it separately.

|`TeamsAppInstallation.ReadWriteForTeam.All`
|Application
|Manages the app lifecycle across teams, including handling version upgrades and removing the app from teams where it is no longer needed.

|`TeamSettings.Read.All`
|Application
|Checks team policies before the app attempts to post. If a team has restricted messaging or moderation enabled, the app surfaces a clear configuration error rather than silently dropping critical API alerts. Read-only — it does not change settings through this permission.

|`TeamSettings.ReadWrite.All`
|Application
|During initial provisioning only, the app may adjust channel settings to enable bot posting in moderated channels where incident alerts must be delivered. This is a one-time setup action, not ongoing runtime behavior.

|`User.Read`
|Delegated
|Standard sign-in permission for the admin performing the initial consent. The app reads basic profile information (name, email) to log who authorized the connection between the Anypoint Platform organization and the Teams tenant.

|===

[[security-data-compliance]]
== Security, Data Retention, and Residency

* *Hyperforce and data boundaries*: The MuleSoft Agent respects your designated Hyperforce region. Install the regional app for Teams that corresponds to your region. Customer data never leaves your designated Hyperforce boundary.
* *LLM architecture and web access*: The MuleSoft Agent uses the Salesforce LLM-Gateway, powered by OpenAI GPT-5-mini. The agent does not perform public web searches.
* *Data retention and compliance*: Data retention policies, data removal, LLM data tenancy, and infrastructure details are covered in the applicable Salesforce Security, Privacy, and Architecture (SPARC) documentation. Customer data is securely deleted upon expiration of the applicable retention periods in accordance with SPARC guidelines. For more information, see the https://www.salesforce.com/company/legal/trust-and-compliance-documentation/[Salesforce Trust and Compliance Documentation].

[[see-also]]
== See Also

Expand Down