Configure agent details and security (Customer Conversation) (preview)

[This article is prerelease documentation and is subject to change.]

The Details and Security tabs in the Shared Settings panel apply across every agent in the orchestration.

Configure agent details

  1. Open your agent in Copilot Studio, and select the Build tab.

  2. Open Shared Settings, and select the Details tab.

  3. Under Agent name and icon, select Change icon to generate, browse, or upload an icon, and update the Agent name.

  4. Under Knowledge, configure:

    • Allow ungrounded responses: Let the agent answer from the model's general knowledge when no connected knowledge source has the answer.
    • Use information from the web: Let the agent search the web to answer questions. This setting uses Grounding with Bing Search, which might send data outside your organization's compliance boundary.
  5. Under File processing capabilities, turn on File uploads to let people attach files (PDF, TXT, CSV, XLSX, and images up to 15 MB) for the agent to analyze in a conversation. Uploaded files are processed per conversation and aren't stored.

Configure security

  1. In Shared Settings, select the Security tab.

  2. Under Agent authentication, select an Authentication mode from the dropdown to control how users sign in to all agents in the orchestration (for example, No authentication).

  3. Under Voice authentication, turn on Voice authentication to require caller verification on voice channels. This setting uses biometric authentication, authentication policies, and OTP challenge rules for voice verification.

    Note

    Voice authentication needs an environment with Dynamics 365 apps enabled. If your current environment doesn't support this, switch to an environment that has Dynamics 365 apps enabled, or move your agent. For steps, see Export and import an agent (Customer Conversation).

    When enabled, configure Biometric Authentication or add the Voice Authentication node to a topic:

    1. Choose what pieces of information are needed to identify users, such as phone number and/or a custom identifier like account number.
    2. Pick the lookup table that uniquely identifies the user. Default tables from Dataverse are provided: Contact and Account.
    3. Select the authentication policy to match the level of authentication needed.

    For more customization, use Advanced editing in Biometric Authentication, or build your own topic with the Voice Authentication node. You can also manage biometric authentication and fraud detection policies in the Microsoft Contact Center Intelligence portal.