W-23753039-EME-08-R2-dm

modules/ROOT/nav.adoc

@@ -12,6 +12,7 @@
     *** xref:exp-services-connect-providers-to-add.adoc[]
     *** xref:exp-services-register-manually.adoc[]
     *** xref:exp-services-create-mcp-server.adoc[]
+    *** xref:exp-services-create-a2a-bridge.adoc[]
     *** xref:exp-instances-add.adoc[]
     *** xref:exp-services-view-details.adoc[]
   ** xref:exp-playground-overview.adoc[]
@@ -22,17 +23,29 @@
     *** xref:model-proxy-policies.adoc[]
     *** xref:model-proxy-request.adoc[]
     *** xref:model-proxy-semantic-service.adoc[]
+    *** xref:model-proxy-semantic-caching-service.adoc[]
     *** xref:model-proxy-try-out.adoc[]
+
   ** xref:exp-scanners-add-from-providers.adoc[]
     *** xref:exp-scanners-prerequisites-reference.adoc[]
     *** xref:exp-scanners-view-details.adoc[]
     *** xref:exp-scanners-manage.adoc[]
     *** xref:exp-providers-manage.adoc[]
+  ** xref:exp-policies-overview.adoc[]
+    *** xref:exp-policies-universal.adoc[]
+    *** xref:exp-policies-apply-manage.adoc[]
+    *** xref:exp-policies-activity-log.adoc[]
+    *** xref:exp-policies-provider-reference.adoc[]
+  ** xref:exp-securing-services.adoc[]
+    *** xref:exp-akamai-risk-correlation.adoc[]
+    *** xref:exp-vaults-manage.adoc[]
+    *** xref:exp-detect-and-contain-rogue-agents.adoc[]
   ** xref:exp-governance-view-cost-and-token-usage.adoc[]
     *** xref:model-proxy-token-reports.adoc[]
-  ** xref:exp-akamai-risk-correlation.adoc[]
-  ** xref:exp-governance-work-with-strategies.adoc[]
+    *** xref:exp-models-manage-costs.adoc[]
+    *** xref:exp-model-wallets-manage.adoc[]
    *** xref:exp-governance-create-strategy.adoc[]
+   *** xref:exp-governance-policy-library-apply.adoc[]
    *** xref:exp-governance-manage-strategies.adoc[]
    *** xref:exp-governance-govern-third-party-apis.adoc[]
    *** xref:exp-governance-monitor-cross-gateway-conformance.adoc[]
@@ -41,6 +54,7 @@
    *** xref:exp-alerts-configure-notifications.adoc[]
   ** xref:exp-connect-with-external-systems.adoc[]
    *** xref:exp-slack-integrate.adoc[]
+   *** xref:exp-teams-integrate.adoc[]
    *** xref:exp-claude-desktop-connect.adoc[]
   ** xref:exp-troubleshoot.adoc[]
    *** xref:exp-ai-assistant-troubleshoot.adoc[]

modules/ROOT/pages/agent-fabric-overview.adoc

@@ -78,6 +78,23 @@ Before agents can orchestrate across your enterprise, your existing systems need
 * When you need it: Use MCP Connector when you need to expose capabilities to agents that require custom logic, multi-system composition, orchestration with external MCP services, or transformation that configuration-based tools like MCP Bridge don’t cover.
 * Learn more: xref:mcp-connector::index.adoc[MCP Connector]
 
+=== A2A Bridge
+
+* What it is: An A2A bridge is an A2A-compliant protocol server that presents an A2A facade in front of an existing non-A2A agent (the source agent). Implemented as a chain of policies—inbound authentication plus the bridge policies—running on an Omni Gateway instance, it translates between the A2A protocol and the agent's native protocol, manages the task lifecycle, and serves A2A task management methods, all without modifying the source agent. Agent Fabric derives an A2A card from the source agent, publishes it to your Portfolio, and deploys the bridge instance from a single wizard.
+
+* Role in Agent Fabric: Agent Fabric can only orchestrate A2A-compliant agents, but many enterprise agents—such as Salesforce Agentforce agents—aren't A2A-compliant on their own. A2A Bridge closes the gap between what your scanners can discover and what Agent Fabric can orchestrate, making non-A2A agents first-class participants in your agent network through configuration alone.
+
+* What you can do:
+** Make a non-A2A source agent A2A-compliant without rebuilding it
+** Customize the advertised A2A card and skills before publishing
+** Deploy the bridge instance to a managed or self-managed Omni Gateway with inbound and upstream authentication
+** Manage the A2A task lifecycle so operations such as `GetTask`, `ListTasks`, and `CancelTask` return correct results
+** Discover, govern, monitor, and orchestrate the bridged agent like any native A2A agent
+
+* When you need it: Use A2A Bridge when you have agents on platforms that aren't yet A2A-compliant (such as Agentforce) and you need Agent Fabric to orchestrate them now. Use A2A Connector instead when you need custom Mule application logic or want to bridge a platform that isn't natively supported.
+
+* Learn more: xref:exp-services-create-a2a-bridge.adoc[]
+
 === A2A Connector
 
 * What it is: Use Anypoint Connector for A2A (A2A Connector) to add A2A protocol support to Mule applications so they can act as both A2A servers and A2A clients. You can also use A2A Connector to make agents built on other platforms A2A-compliant.

modules/ROOT/pages/exp-akamai-risk-correlation.adoc

@@ -66,7 +66,7 @@ Akamai periodically pulls API instance and asset information from MuleSoft (typi
 Akamai to MuleSoft::
 The scanner pulls security findings and incidents from Akamai on the schedule you set, then correlates and stores them so they appear on the related services in *Portfolio*.
 
-For Akamai to observe and correlate traffic, the Akamai correlation policy must be applied to your API instances. This out-of-the-box policy (for Flex Gateway and Mule gateways) stamps correlation headers on API responses so Akamai can match observed traffic to the correct MuleSoft API. Akamai observes north-south traffic only for domains you own and control.
+For Akamai to observe and correlate traffic, the Akamai correlation policy must be applied to your API instances. This out-of-the-box policy (for Omni Gateway and Mule gateways) stamps correlation headers on API responses so Akamai can match observed traffic to the correct MuleSoft API. Akamai observes north-south traffic only for domains you own and control.
 
 == Review Scanner Detail Tabs
 
@@ -95,6 +95,7 @@ After a successful run, Akamai results appear on existing services:
 * API list views show values in the *Security Risk* column.
 * API detail pages show Akamai security data in *Conformance*.
 * Security sections display violation totals, findings, incidents, and endpoint context.
+* The *Akamai Security Findings* table lists each finding with columns for finding, instance, endpoint, API risk, scan status, and remediation progress.
 * Finding detail views show fields such as status, type, endpoint path, and mapped frameworks.
 
 == Interpret Risk Status Levels
@@ -113,6 +114,29 @@ Elevated risk. Investigate and remediate first.
 Critical::
 Highest urgency risk. Remediate immediately.
 
+== Track Remediation and Scan Status
+
+In the *Akamai Security Findings* table on the *Conformance* tab, two columns help you track remediation progress for each finding:
+
+Remediation::
+Shows how many of the suggested remediation policies are applied on the finding's instance, as an _applied/suggested_ count (for example, `1/3 remediations`). The suggested count reflects the remediation policies recommended for that finding type, and the applied count reflects how many of those policies are currently applied on the API instance. This count is tracked at the instance level, so two findings on different endpoints of the same instance that share a finding type show the same count.
+
+Scan Status::
+Indicates whether remediation is underway for the finding:
++
+--
+Open:::
+No remediation policy is applied yet for the finding.
+
+Rescan Confirmation:::
+At least one remediation policy is applied on the instance, but the finding still appears in the latest results. Re-run the scanner to confirm whether the finding is resolved.
+--
+
+[NOTE]
+====
+The *Akamai Security Findings* table lists only findings that are currently active. When a finding is remediated and a rescan confirms the fix, the finding no longer appears in the table.
+====
+
 == Remediate Risks from the API Conformance Tab
 
 Use the API *Conformance* tab in *Portfolio* to triage and remediate Akamai findings:

modules/ROOT/pages/exp-alerts-configure-notifications.adoc

@@ -1,7 +1,7 @@
 = Configuring Notifications for Alerts
 :keywords: alerts, notifications, configure alerts, alert target, manage alerts, anypoint platform, monitoring
 
-Send API Manager alerts from Anypoint Platform directly to Slack channels and email. Configure alerts in the enhanced experience so teams can see notifications where they work and jump directly into *Portfolio* or *Observability* to respond.
+Send API Manager alerts from Anypoint Platform directly to Slack channels, Microsoft Teams channels, and email. Configure alerts in the enhanced experience so teams can see notifications where they work and jump directly into *Portfolio* or *Observability* to respond.
 
 == Before You Begin
 
@@ -23,7 +23,7 @@ Before getting started, make sure you have:
 +
 For more information, see xref:exp-home-start.adoc#permissions[Enhanced Experience Permissions].
 
-* The MuleSoft Slack app installed in your workspace (see xref:exp-slack-integrate.adoc[] for installation steps)
+* The MuleSoft Slack app installed in your workspace (see xref:exp-slack-integrate.adoc[] for installation steps), or the MuleSoft for Teams app installed in your Microsoft Teams tenant (see xref:exp-teams-integrate.adoc[] for installation steps)
 
 == View and Manage Alerts
 
@@ -34,7 +34,7 @@ The enhanced experience provides a unified view of all your alerts:
 . Filter alerts by:
 ** Alert type (request count, response time, response codes, and policy violation)
 ** Severity level (critical, warning, informational)
-** Delivery channel (Slack, email, both)
+** Delivery channel (Slack, Microsoft Teams, email)
 
 == Create an Alert
 
@@ -76,9 +76,13 @@ This name appears in the notification list and email subjects.
 . Configure *Delivery Channels*:
 ** Toggle *Email* on or off to send alerts to email addresses.
 ** Toggle *Slack* on or off to send alerts to Slack if enabled.
+** Toggle *Microsoft Teams* on or off to send alerts to Teams if enabled.
 . If *Slack* is enabled, select your delivery destination:
 ** Choose a Slack channel from your workspace.
 ** Or select a direct message recipient.
+. If *Microsoft Teams* is enabled, select your delivery destination:
+** Choose a Teams channel from your tenant.
+** Or select a direct message recipient.
 . Click *Create Alert* to save.
 
 == Edit an Existing Alert
@@ -91,12 +95,12 @@ To modify an existing alert:
 . Update any section as needed:
 ** *Select Alert Target*: Change the environment, service type, target service, or API instance.
 ** *Specify Alert Configuration*: Modify the metric, condition, threshold, or time window.
-** *Set Alert Delivery*: Change severity, alert name, or delivery channels (Email, Slack).
+** *Set Alert Delivery*: Change severity, alert name, or delivery channels (Email, Slack, Microsoft Teams).
 . Save your changes.
 
-== Slack Alert Notifications
+== How Alerts Appear in Slack and Microsoft Teams
 
-When an alert triggers, your team receives a notification directly in the configured Slack channel or DM:
+When an alert triggers, your team receives a notification directly in the configured Slack or Microsoft Teams channel or DM:
 
 * Alerts display key information about the condition that triggered them
 * Teams can see and respond to alerts where they already collaborate
@@ -120,3 +124,5 @@ This routing strategy ensures teams see the most important signals first without
 * xref:exp-services-view-detailed-metrics.adoc[]
 * xref:exp-home-start.adoc[]
 * xref:exp-overview.adoc[]
+* xref:exp-teams-integrate.adoc[]
+* xref:exp-slack-integrate.adoc[]

modules/ROOT/pages/exp-compare.adoc

@@ -13,7 +13,7 @@ Unified Relationships Across Entity Types:: *Overview* and graph-style context s
 Governance Framed for AI as Well as APIs:: You apply and review governance across domains such as access and security, performance and cost, data privacy and integrity, and compliance and observability, aligned to the asset you're viewing. Policy and conformance work stays adjacent to the asset instead of only in a separate API-only mental model.
 Cost and Usage Signals for AI Operations:: The experience includes cost management tooling aimed at portfolio spend, including visibility into token usage and optimization strategies for MCP servers and related AI paths. Use it when you need instance-level usage context tied to the same catalog as the rest of the portfolio.
 Instance-Level Policy Control:: For instances backed by Omni Gateway where the product supports it, the experience elevates instance-level governance, including options to tune policy order and draw from a named policy catalog. Use the enhanced experience when you need fine-grained control in the portfolio UI, and use the deeper runtime-only workflows in Anypoint Platform when the experience links you there.
-Provider Breadth for AI Connections:: *Platform* includes *Providers* and related configuration so the experience can connect AI and integration services across multiple vendors, such as AWS Bedrock and Google Vertex AI, in addition to your existing MuleSoft footprint. The interface supports multi-vendor AI stacks without forcing each vendor's console to be your only view.
+Provider Breadth for AI Connections:: *Platform* includes *Providers* and related configuration so the experience can connect AI and integration services across multiple vendors, such as AWS Bedrock and Google Vertex AI, in addition to your existing MuleSoft footprint. The same *Providers* area connects external vaults (AWS Secrets Manager, Microsoft Azure Key Vault, and HashiCorp Vault), so credentials stay in your existing secrets manager instead of in your MuleSoft configuration. The interface supports multi-vendor AI stacks without forcing each vendor's console to be your only view.
 Managed and Unmanaged Instances:: The experience supports creating managed instances on Omni Gateway when you want full support paths including authentication and monitoring, or unmanaged-style instances when you want a lighter footprint. Select the model per asset and gateway strategy.
 Assistant Across the Portfolio:: The in-product MuleSoft Agent assistant targets setup, questions, and recommendations across the services the experience tracks. The classic Anypoint Platform control plane doesn't provide that same assistant-led experience.