Case Study 1 - Blue Yonder Airlines
Background
Blue Yonder Airlines is a global carrier headquartered in Los Angeles, California, operating domestic and international flights. The company serves millions of passengers annually through its website, mobile app, and call centers. To improve customer service efficiency and reduce call center volume, Blue Yonder is deploying an AI agent in Microsoft Copilot Studio.
The agent will handle customer inquiries across multiple channels - web chat, mobile app, and Microsoft Teams (for internal support staff). It will answer questions, retrieve data from enterprise systems, and escalate to human agents when needed.
The project is led by a cross-function team:
- Product manager: Defines requirements and success metrics.
- Lead agent author: Designs topics, intents, and generative behavior.
- Flow designers: Build agent flows and integrations.
- IT/security and compliance: Oversees identity, data protection, and Responsible AI (RAI) compliance.
Current environment
Channels
Public website: Embedded web chat
Mobile app: In-app chatbot
Microsoft Teams: Internal support agent access
Identity and access
Customers: Anonymous access for general inquiries (e.g., flight status, baggage policy).
Authentication is required for personal data access (e.g., bookings, loyalty points).
Internal staff: Authenticate via Microsoft Entra ID.
Data sources
Reservation and Ticketing System (internal): REST API, no prebuilt connector with custom enterprise database.
Flight Status and Weather APIs (external): REST APIs with API keys.
Customer Support Knowledge Base: SharePoint library with PDFs and policy documents.
Loyalty Program Data: Stored in Dynamics 365 and Dataverse.
Travel Advisory Content: Uses REST API with partner services.
Integration mechanisms
Custom connectors must be used for internal APIs that lack prebuilt connectors.
HTTP request nodes may be used for lightweight external APIs.
Knowledge sources must be used for unstructured content.
Agent flows must be used to encapsulate reusable logic (e.g., rebooking).
Business requirements
Omnichannel support
Deploy the agent across web, mobile, and Teams with a consistent user experience. The Teams deployment must also support internal staff.
Self-service capabilities
The agent must handle common inquiries such as:
- Flight status
- Booking and rebooking
- Loyalty program questions
- Travel policies and baggage rules
Human escalation
If the agent cannot resolve an issue or the user requests help, it must:
- Escalate to a human agent.
- Transfer the conversation transcript and relevant context.
- Redact any sensitive personal data before escalation.
Knowledge integration
The agent must use scalable methods for knowledge integration and must not rely on manually authored Q&A topics for each document.
Performance metrics
First-contact resolution: +25%
Tier-1 call deflection: ≥20%
Response time: 90% of queries answered within 30 seconds
Accuracy: ≥95% for known FAQs
CSAT: ≥85% for AI-handled interactions
Technical requirements
Platform constraints
No custom code is permitted; only Copilot Studio's built-in tools may be used.
All backend logic must be implemented using agent flows.
Markdown must be used for formatting (e.g., bold, bullet points); HTML is not supported.
Authentication
Sign-in is required for personal data access.
Anonymous access is allowed for general inquiries.
User identity must be used for data access; shared or builder credentials must not be used.
Compliance and security
Power Platform DLP policies must be enforced to block unauthorized data flows.
Responsible AI content moderation filters must be enabled.
Prompt modifications must be added to enforce tone, disclaimers, and refusal behavior.
Disclaimers must be applied consistently across all generative responses. Manual edits to individual topics must be avoided.
Monitoring and maintenance
All conversations and actions must be logged for auditing.
Weekly reviews of transcripts and metrics must be conducted.
Topics, flows, and knowledge sources must be updated as policies or systems evolve.
Issues and constraints
API rate limits: External APIs (e.g., flight status) have usage limits. Agent flows must handle retries and caching to avoid exceeding quotas.
Knowledge base limits: Copilot Studio has limits on the number and size of indexed documents.
Large files must be split or summarized.
Generative answer risks: Generative responses must be constrained to avoid policy violations.
Prompt modifications and filters must be used to enforce tone, safety, and compliance.
User input variability: Users phrase questions in diverse ways. Topics must include varied trigger phrases and fallback handling.
Authentication UX: The agent must clearly explain when sign-in is required and handle transitions smoothly across channels.
Problem statement
Blue Yonder Airlines must deploy a secure, scalable, and policy-compliant AI agent using Microsoft Copilot Studio. The agent must deliver accurate, helpful, and safe responses across multiple channels, integrate with enterprise systems, and support both anonymous and authenticated users. It must adhere to strict data protection and Responsible AI standards while improving customer service efficiency and satisfaction.
You need to ensure that every AI-generated response from the agent in Copilot Studio includes a disclaimer that complies with the company's security and governance policies.
Which two actions should you perform? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.

• A.Add a greeting message that includes the disclaimer.
• B.Add a prompt modification in the generative answers node settings.
• C.Create a disclaimer topic that always runs first.
• D.Disable generative answers and use only pre-authored responses.
• E.Edit every topic's first message to include the disclaimer.

Comment: *

Name: *

Email: *

Verification: *

Drag and Drop Question
A company plans to use Copilot connectors to ground answers from a third-party system for an agent in Copilot Studio.
To meet the business needs, responsibilities for configuring and using Copilot connectors must be separated, based on the following requirements:
- For tenant administration, the connector must be available at the
tenant level.
- For agent runtime behavior, answers must be grounded from authorized
sources.
- For builder configuration, you must add the connector to the agent.
You need to determine how Copilot connector set-up responsibilities are handled across tenant, runtime, and builder stages.
What should you configure for each requirement? To answer, move the appropriate configuration to the correct requirements. You may use each configuration once, more than once, or not at all.
You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.

Correct Answer:

Explanation:
Box 1: Configure the Copilot connector in Microsoft 365 Admin Center
To make a Copilot connector available at the tenant level for grounding agent responses in Microsoft Copilot Studio, you must configure and deploy the connector in the Microsoft 365 Admin Center.
Tenant Administration (Microsoft 365 Admin Center): Tenant administrators must configure and deploy the specific Copilot connector (e.g., ServiceNow, Salesforce, Box) within the Microsoft 365 Admin Center. This process indexes the necessary content from your third-party system across the enterprise so it can be utilized by your organization's agents.
Box 2: Add the Copilot connector as a knowledge source
To use a Copilot connector as an enterprise knowledge source in Microsoft Copilot Studio, the prerequisite configuration requires the builder to add the Copilot connector as a knowledge source.
The Builder Stage: While your AI or tenant administrator is responsible for deploying and configuring the Copilot connector in the Microsoft 365 admin center, the builder stage handles agent-specific knowledge mapping. [Box 3 below] Knowledge Integration: As an agent builder, you must actively select the preconfigured Copilot connector from the available list and add it as a knowledge source to your agent's generative answers node.
Runtime Behavior: Once this is configured, the Copilot engine indexes and queries the third-party data securely at runtime. Because the connector is tied to your tenant's security parameters, the agent will only ground answers using authorized sources and fully respect source-level permissions.
Box 3: Configure the Copilot connector in Microsoft 365 Admin Center
The initial deployment and central management of a Copilot connector must be performed in the Microsoft 365 Admin Center by a tenant administrator. However, completing the builder configuration to add the connector as a knowledge source for a specific agent is done directly within Microsoft Copilot Studio.
Reference:
https://learn.microsoft.com/en-us/microsoft-365/copilot/connectors/deployment-overview

Comment: *

Name: *

Email: *

Verification: *

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear on the review screen.
A team is implementing ALM for agents in Copilot Studio across multiple environments.
The team requires a consistent way to manage and transport agent assets.
You need to recommend a solution that supports creation and use of ALM scenarios for agents in Copilot Studio.
Solution: Builders can change environment variable values directly in Copilot Studio to complete ALM configuration without administrative tools.
Does the solution meet the goal?

• A.Yes
• B.No

Comment: *

Name: *

Email: *

Verification: *

A company has an approved custom connector that uses a REST API for an internal system.
An agent in Copilot Studio must call this connector during conversations to retrieve or update data.
To meet the business needs, the solution must meet the following requirements:
Make the connector actions available for the agent to invoke.
Ensure authentication is handled at the service level, not per user.
Pass conversation context into the connector when it is called.
Surface the returned data of the connector to the user in the conversation.
You need to configure the agent and the connector action to meet the requirements.
What should you configure for each requirement? To answer, move the appropriate configurations to the correct requirements. You may use each configuration once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.

Correct Answer:

Comment: *

Name: *

Email: *

Verification: *

You need an agent to only be invoked by other trusted agents in the tenant, not directly by end users. What should you configure?

• A.Publish the agent to the public web channel
• B.Configure the agent as a connected agent without exposing a standalone chat channel
• C.Enable anonymous authentication
• D.Increase the token limit

Comment: *

Name: *

Email: *

Verification: *