Making a Copilot Studio bot publicly accessible with Dataverse knowledge

(0) Share

Report

Posted on by JL-07080908-0

Hello everyone,

I am in the process of developing a bot via Copilot Studio and I have integrated knowledge from Dataverse, including data from my CRM Dynamics 365.
My goal is to make this bot accessible on a website, without users needing to log in.

However, I am encountering a difficulty:
➡️ The knowledge from Dataverse is not accessible without authentication, especially if I want to use it in a generating response.

Is there a method to expose this knowledge to a bot without requiring user authentication?

Thank you in advance for your feedback and suggestions

Categories:

Power Platform integration

I have the same question (0)

All responses (1)

Answers (0)

Suggested answer

DAnny3211 10,139 Moderator on at

Like (0)

Report
Making a Copilot Studio bot publicly accessible with Dataverse knowledge

Hi there,

This is a great use case, and you're right—accessing Dataverse knowledge without authentication presents a challenge due to the platform's security model.

Here's what you should know and consider:

1. Dataverse Requires Authentication

By design, Dataverse enforces authentication to protect sensitive business data. This means bots using Dataverse data for generating responses will require authenticated access, even if the bot itself is public.

2. Workaround Options

If you want to make the bot publicly accessible without requiring users to log in, consider these alternatives:

Use an External Data Layer: Create a lightweight API or Azure Function that exposes only the necessary data from Dataverse. This API can be called by the bot without requiring user authentication, but you must ensure it doesn’t expose sensitive information.

Cache Public Data: If the data is not sensitive and doesn’t change frequently, you could cache it in a public data source (e.g., Azure Blob Storage or a public-facing database) and connect your bot to that instead of Dataverse directly.

Use Power Pages: If you're open to using Power Pages, you can embed the bot there and control access to Dataverse data via authenticated sessions, while still offering a public-facing experience.

3. Security Considerations

Always ensure that any public exposure of data complies with your organization’s data governance and privacy policies. Even seemingly harmless CRM data can be sensitive in the wrong context.

Let me know if you'd like help setting up an API layer or exploring Power Pages integration.

If this answer was helpful, please consider marking it as accepted.
Best regards,
Daniele

Was this reply helpful? Yes No