--- schema_version: "1" id: 906572597702b758cbc6a12d307a025a6f7424b9b7bad1eecc5980d6a3507537 title: Viewing and Managing Provider Connections collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/general/exp-providers-manage.md canonical_url: https://docs.mulesoft.com/general/exp-providers-manage source_site: docs.mulesoft.com content_type: documentation content_hash: 26b988a07cd79075c404792fa960e4476e880d0d3054eecd31232c19e1472ba3 description: MuleSoft Documentation Site latest: true --- --- product: Getting Started keywords: providers, scanners, providers page, provider list, view providers, manage providers, anypoint platform --- # Viewing and Managing Provider Connections > For the full documentation index, see: https://docs.mulesoft.com/llms.txt The **Providers** page shows which cloud platforms and API management systems are connected to the enhanced experience. From **Platform** > **Providers**, you can view connected providers, filter scanners by provider, and connect new providers to begin discovering services. ## Before You Begin Before getting started, make sure you have: - An Anypoint Platform account. - Exchange Administrator permission. For more information, see [Enhanced Experience Permissions](https://docs.mulesoft.com/general/exp-home-start#permissions). ## Access the Providers Page 1. Sign in to the enhanced experience through your organization’s entry point. 2. In the navigation, select **Platform** > **Providers**. The **Providers** page displays the provider list and scanner list. ### Provider List The side panel shows providers organized into two groups: Connected Providers that have active scanner connections. Each connected provider card shows the provider name, logo, number of discovered services, and number of configured scanners. Not Connected Providers available for connection but not yet configured. Select a not-connected provider to begin the scanner setup workflow. The workflow guides you through the process of connecting the provider and configuring the scanner. ### Scanners List Select **All Providers** to view all scanners across all connected providers. The main panel displays the scanner list. The scanner list shows: - **Scanner Name**: The scanner identifier and provider platform - **Services**: Count of services discovered by this scanner - **Last Scanned**: Time since the last successful scan - **Scan Trigger**: Schedule type (Scheduled, Manual, or On-Demand) ## Filter Scanners by Provider To view scanners for a specific provider, select the provider from the sidebar. The scanner list updates to show only scanners configured for that provider. ## View Scanner Details To see detailed information about a scanner, including scan history, activity log, and configuration, select the scanner name in the scanner list. The scanner detail page includes **Overview**, **Services**, and **Settings** tabs. For detailed tab behavior and scanner-type differences, see [Viewing Scanner History and Settings](https://docs.mulesoft.com/general/exp-scanners-view-details). For information about managing scanners, see [Running and Managing Scanners](https://docs.mulesoft.com/general/exp-scanners-manage). For Akamai-specific setup and result interpretation, see [Correlating Risk Using Akamai API Security](https://docs.mulesoft.com/general/exp-akamai-risk-correlation). ## Connect a New Provider To add a provider connection: 1. From **Platform** > **Providers**, select a provider from the **Not Connected** section. 2. Follow the connection workflow to authenticate and configure scanner settings. The wizard walks through three steps: **Choose Provider**, **Connect to Provider**, and **Connection Setup**. For Microsoft Copilot Studio scanners, select **OAuth (Authorization Code)** and complete authorization in the Microsoft sign-in popup before you continue. For details, see [exp-scanners-add-from-providers.adoc#microsoft-copilot-studio-scanner-oauth-authorization](https://docs.mulesoft.com/general/exp-scanners-add-from-providers#microsoft-copilot-studio-scanner-oauth-authorization). For detailed scanner setup instructions, see [Adding Scanners from Providers](https://docs.mulesoft.com/general/exp-scanners-add-from-providers). > [!NOTE] Amazon, Microsoft, and HashiCorp also support registering an external vault instead of a > scanner. A vault syncs secret metadata rather than discovering services, so it doesn’t populate a > **Portfolio** catalog. For the vault registration flow, see > [Using Credentials Stored in External Vaults](https://docs.mulesoft.com/general/exp-vaults-manage). ## Akamai API Security Data in Portfolio When Akamai API Security is connected and scans have completed, security risk data appears on the detail pages of scanned APIs: - A **Security Risk** column in the **Instances** tab shows a color-coded risk level per instance: Low, Medium, High, or Critical. - An **Akamai** section in the **Conformance Report** tab shows full findings and incidents from the scan. In list and card views, the numeric value shows Akamai correlation policy coverage (applied policies compared to total required policies), while the color-coded **Security Risk** label (Low, Medium, High, or Critical) shows the severity level of correlated security findings. ## Supported Providers The enhanced experience supports connections to these providers: - Akamai - Amazon - Anthropic - Databricks - GoDaddy - Google - HashiCorp - Kong - LangChain - Microsoft - Salesforce - ServiceNow - Snowflake > [!NOTE] When scanning Kong, the enhanced experience discovers gateway-level plugin information in > addition to services. > > **Akamai API Security** is available only when your administrator has enabled the feature for your > organization. When enabled, it appears in the **Not Connected** section of the Providers sidebar. Of these providers, the API gateway providers Google (Apigee), Kong, and Microsoft (Azure API Management) support policy write. APIs discovered by a connection that has only read access to the provider appear as **Read-Only**, and policy actions are unavailable until the connection’s identity is granted the provider’s write scope. For provider-specific read and write scopes, see [Policy Write Prerequisites](https://docs.mulesoft.com/general/exp-scanners-prerequisites-reference#_policy_write_prerequisites). The specific providers available depend on your organization’s enabled products and enhanced experience configuration. ## See Also - [Create a Scanner for Provider Services](https://docs.mulesoft.com/general/exp-services-connect-providers-to-add) - [Correlating Risk Using Akamai API Security](https://docs.mulesoft.com/general/exp-akamai-risk-correlation) - [Viewing Scanner History and Settings](https://docs.mulesoft.com/general/exp-scanners-view-details) - [Adding Scanners from Providers](https://docs.mulesoft.com/general/exp-scanners-add-from-providers) - [Running and Managing Scanners](https://docs.mulesoft.com/general/exp-scanners-manage) - [Adding Services to Your Portfolio](https://docs.mulesoft.com/general/exp-services-add-to-portfolio) - [Using Credentials Stored in External Vaults](https://docs.mulesoft.com/general/exp-vaults-manage)