An organization is using Power Virtual Agents (now Copilot Studio) to create a customer service chatbot. The chatbot must be available only to users inside the organization, not to external customers. What should the administrator do?
Configuring authentication restricts the chatbot to signed-in organisational users, since only internal identities can obtain valid credentials. This satisfies the requirement that the bot be unavailable to external customers, who cannot authenticate against the tenant.
Why this answer
The correct answer is A. To restrict a Power Virtual Agents (Copilot Studio) chatbot to internal users only, the administrator should configure authentication in the chatbot. This enforces sign-in and limits access to users within the organization's Azure AD tenant, preventing external customers from interacting with it.
Exam trap
The trap is assuming that environment creation or analytics settings control access, when the actual access control mechanism for a chatbot is its authentication configuration.
How to eliminate wrong answers
Option B is wrong because publishing the chatbot to a public website makes it accessible to anyone on the internet, which is the opposite of the requirement. Option C is wrong because creating a new environment does not by itself restrict access; environments are containers for solutions and data, not an authentication boundary for chatbot users. Option D is wrong because disabling analytics affects telemetry and reporting, not user access control.