AB-731 AI Transformation Leader Questions and Answers

Answer Area

The marketing department at your company wants AI to summarize emails and create presentations. Answer: Use Microsoft 365 Copilot

The HR department at your company wants a conversational agent for policy questions and leave requests. Answer: Build with Microsoft Copilot Studio

The manufacturing department at your company wants AI to predict maintenance schedules. Answer: Build with Azure Machine Learning

The finance department at your company wants AI-powered access to enterprise resource planning ERP data by using familiar productivity tools. Answer: Extend with Microsoft 365 Copilot connectors

These scenarios map to four distinct solution patterns: out-of-the-box productivity assistance, low-code conversational agents, predictive ML, and enterprise data integration.

Marketing’s need to summarize emails and create presentations is a core “productivity copilot” use case. Microsoft 365 Copilot is embedded in Outlook, Word, PowerPoint, and Teams, so it directly supports summarization, drafting, and presentation generation without building a custom solution—making Use Microsoft 365 Copilot the best fit.

HR’s requirement is a conversational agent tailored to internal policies and workflows such as leave requests. That typically needs custom dialog, grounded knowledge sources, and possibly actions/workflows. Microsoft Copilot Studio is designed to build and manage such agents with organizational knowledge and business process integration, so Build with Microsoft Copilot Studio fits best.

Manufacturing’s predictive maintenance scheduling is classic predictive analytics: learning patterns from historical telemetry/maintenance data to forecast failures or optimal service windows. This is best addressed with Azure Machine Learning , which supports training, evaluating, and deploying custom predictive models.

Finance wants AI-powered access to ERP data “using familiar productivity tools,” which implies bringing external line-of-business data into the Microsoft 365 Copilot experience. That is precisely where Microsoft 365 Copilot connectors help—indexing and exposing enterprise data sources so Copilot can reference them in a governed way—so Extend with Microsoft 365 Copilot connectors is the best approach.

Answer Area

A generative AI solution is well-suited to predict next-quarter sales trends. Answer: No

A generative AI solution can summarize lengthy policy documents. Answer: Yes

A generative AI solution can create product descriptions from product specifications. Answer: Yes

No — Predicting next-quarter sales trends is primarily a forecasting/predictive analytics problem. Microsoft differentiates predictive AI (forecasting outcomes from historical patterns) from generative AI (creating content like text, images, or code). While you can use LLMs to assist analysts (explain trends, draft narratives), the core forecasting model is typically traditional ML/time-series methods rather than generative AI as the main engine.

Yes — Summarization is a classic, high-value generative AI capability. Given a long policy, an LLM can compress it into executive summaries, key obligations, risks, and action items, often with formatting constraints (bullets, sections, “do/don’t” lists). Microsoft highlights summarization and analysis as common generative AI use cases in business contexts.

Yes — Generative AI is well-suited to transform structured inputs (features/specs) into natural-language outputs (product descriptions). This is straightforward “content generation,” where you control tone, length, and required fields (benefits, differentiators, disclaimers). Microsoft also points to generating product descriptions and similar marketing/customer-facing text as a practical generative AI scenario.

An AI governance council (often called an “AI Council”) exists primarily to set direction and provide cross-functional oversight so AI adoption stays aligned to the organization’s values, risk posture, and Responsible AI commitments. That maps most directly to D . Microsoft’s guidance on creating an AI Council describes leadership responsibilities such as defining and communicating the organization’s AI vision, values, and policies , reviewing and approving AI use cases/projects, and coordinating with enablement and technical readiness teams to understand risks, issues, and opportunities. It also emphasizes representation across distinct functions (for example: senior leadership, legal, compliance, risk, ethics, data, technology, business, HR) to ensure governance decisions reflect a broad, accountable perspective.

The other options describe activities that may be supporting outcomes of governance, but they are not the council’s primary purpose. A is narrow (IT policy enforcement/user monitoring) and is typically handled by security/compliance operations rather than the top-level governance body. B is user enablement/training (commonly owned by adoption/change management teams). C focuses on technical delivery and performance management (often owned by engineering/MLOps/service owners). The governance council’s central value is strategic guidance + oversight + cross-functional alignment to ensure Responsible AI adoption is consistent, accountable, and sustainable across the business.

Answer: crafting clear instructions to guide generative AI solutions in generating context-appropriate content.

Prompt engineering is fundamentally about how you communicate intent to a generative AI model so it produces outputs that meet business expectations. The best completion is “crafting clear instructions to guide generative AI solutions in generating context-appropriate content” because it captures the practical, day-to-day discipline: shaping the input (prompt) with the right task framing, constraints, context, and output format.

In real deployments, prompt engineering includes specifying the role and objective (for example, “act as a customer support agent”), providing the necessary context (product details, policy excerpts, audience), adding explicit requirements (tone, length, must/must-not statements), and defining structured output (JSON fields, bullet sections, headings). It can also include adding examples (few-shot prompting), clarifying what to do when information is missing, and instructing the model to cite only provided sources or to ask follow-up questions. These techniques reduce ambiguity, improve consistency, and lower the risk of hallucinations or off-brand responses.

The other options are not accurate definitions. “Integrating AI-powered tools into business workflows” describes solution adoption/integration, not prompt engineering. “Identifying and fixing errors in AI-generated content” is review/editing or quality assurance. “Designing, developing, and training generative AI models” is model development/ML engineering. Prompt engineering operates without changing model weights ; it’s about steering model behavior through well-constructed instructions and context.

Microsoft 365 Copilot is designed to work within the Microsoft 365 ecosystem and use organizational context that is already governed by Microsoft Entra ID, Microsoft 365 permissions, and compliance controls. By default, Copilot can use Microsoft Graph signals and content that exist in Microsoft 365 workloads the user already has access to—most commonly emails, files, meetings, and chats . That corresponds to A .

The key concept is permission-trimming: Copilot doesn’t magically gain access to everything; it can only surface or use data that the signed-in user is permitted to access in Microsoft 365. This is what makes Copilot valuable for productivity scenarios—summarizing email threads, drafting replies, generating meeting recaps, creating documents from your files, or pulling context from Teams chats—because those artifacts are already part of daily work and already subject to tenant policies.

The other options are not “by default” Microsoft Graph content for Copilot: B (file shares) typically requires additional integration or migration into Microsoft 365 repositories or indexing via connectors; it’s not inherently available. C is unrelated to Microsoft 365 tenant work data. D (public web) is not “information in Microsoft Graph”; web grounding is a separate capability and not the default Graph workload data source referenced here.

Answer Area

Content filtering controls can prevent AI-generated responses from exposing confidential and sensitive information. Answer: Yes

AI-generated content can unintentionally reveal sensitive information if the generative AI model has access to unsecured data sources. Answer: Yes

To prevent data exposure, only the prompts used by users must be protected by using policies. Answer: No

Yes — Content filtering (and related safety controls) can help reduce the chance that responses contain policy-violating or sensitive outputs by detecting and blocking certain categories of content. While filtering is not a perfect guarantee, it is a recognized control to prevent or reduce exposure risk in outputs (for example, blocking regulated data patterns, disallowed content categories, or unsafe disclosures).

Yes — If a model (or the solution’s retrieval layer) can access poorly governed repositories—such as broadly shared folders, misconfigured SharePoint sites, or unsecured databases—then the system can surface sensitive information in responses even without malicious intent. This is why access control, data classification, and permission hygiene are critical prerequisites for deploying AI assistants grounded in organizational content.

No — Protecting only user prompts is insufficient. Data exposure can occur through multiple paths: retrieved documents, generated outputs, logs/telemetry, training/fine-tuning data, and connector/index configuration. Preventing exposure requires layered controls: data governance (labels, DLP, least privilege), secure connectors, output filtering, auditing, and user training—not prompt policy alone.

The requirement is specific: users must build and use declarative agents that can access work data (tenant data / organizational context). Microsoft’s licensing guidance for Copilot extensibility ties use of declarative agents to having the appropriate Copilot entitlement that enables tenant grounding and organizational data access. In Microsoft’s cost and licensing considerations for declarative agents, Microsoft states that to use a declarative agent, users must have a Microsoft 365 Copilot add-on license (or an equivalent Copilot Chat add-on path tied to eligible licensing). Therefore, among the provided options, the best recommendation is A.

Option B (Copilot Studio user license) is primarily about authoring/building agents in Copilot Studio, but it is not, by itself, the licensing prerequisite that grants end users the right to use those agents with full Microsoft 365 Copilot capabilities and work-data grounding inside the Microsoft 365 Copilot environment. Publishing/building can be separate from the end-user entitlement to use the agent with organizational context.

Option C (Copilot Chat pay-as-you-go) can enable usage-based access to declarative agents in some configurations, but the question asks for the best license recommendation for users who need work-data access through declarative agents. The Microsoft 365 Copilot add-on is the straightforward, fully supported entitlement for that scenario.

For a proof of concept , the key requirements are low commitment , quick start , and the ability to scale up or down as you learn what real usage looks like. Azure OpenAI Standard On-Demand pricing is designed for exactly that: you pay per token consumed (input and output) on a pay-as-you-go basis, which makes it ideal when demand is uncertain or variable—typical in early pilots and PoCs.

By contrast, Provisioned (PTUs) is best when you have well-defined, predictable throughput and latency requirements —usually a more mature, production workload. PTUs involve reserving model processing capacity to achieve consistent performance and more predictable costs, which is usually premature for a PoC where actual traffic patterns are not yet known.

Batch API is optimized for asynchronous high-volume jobs with a target turnaround (for example, up to 24 hours) and discounted pricing. That’s great for offline processing, but it does not match an interactive “agent” PoC that typically needs near-real-time responses and iterative testing.

Microsoft 365 Copilot is a separate SaaS licensing model and is not the Azure OpenAI pricing model for building your own agent solution.

Answer Area

Microsoft Copilot provides a single AI app that has identical features and experiences across all Microsoft products. Answer: No

Microsoft 365 Copilot delivers AI capabilities for business users that use Microsoft 365 apps. Answer: Yes

Microsoft Security Copilot helps companies understand risks and the organizational security posture. Answer: Yes

No — “Copilot” is an umbrella brand across Microsoft, but the experiences are not identical . Different Copilots target different workloads (productivity, security, development, business apps) and therefore expose different capabilities, connectors, permissions models, and admin controls. For example, Microsoft 365 Copilot is embedded in Word/Excel/PowerPoint/Outlook/Teams, while Security Copilot is built for SOC workflows and integrates with security tooling; they are intentionally not the same app with the same features.

Yes — Microsoft 365 Copilot is specifically designed to deliver generative AI assistance for users working in Microsoft 365 applications . It enhances common business tasks such as drafting, summarizing, meeting recap, creating presentations, and working with documents and communications—directly inside the Microsoft 365 productivity suite.

Yes — Microsoft Security Copilot is focused on security operations and helps analysts understand threats, investigate incidents, and improve visibility into security posture. Its purpose is aligned with helping organizations interpret security signals and risk context more efficiently, which supports understanding organizational risk and posture.

Answer Area

Using incomplete or poor-quality data during generative AI model training can increase costs. Answer: Yes

AI models rely on training data to learn patterns and identify relationships to produce outputs. Answer: Yes

Generative AI models trained on non-representative datasets can produce inaccurate or unbalanced results. Answer: Yes

Yes — Poor-quality or incomplete training data increases cost because it drives more iterations: additional data cleaning, relabeling, re-training, and re-evaluation to reach acceptable performance. It can also increase operational costs after deployment if the model produces low-quality outputs that require human rework, escalations, or incident handling. In practice, data quality debt becomes model cost debt.

Yes — Training data is the primary mechanism by which AI models learn statistical patterns and relationships. For generative models, the training corpus shapes language fluency, factual associations, style tendencies, and the kinds of content the model can produce. Without sufficient and appropriate training signals, outputs degrade.

Yes — If the training dataset is not representative of the real-world population or business context, the model can systematically underperform for certain groups, topics, or edge cases. This can manifest as biased language, missing perspectives, and uneven accuracy, producing “unbalanced” results. That is why Responsible AI practice emphasizes representative data, evaluation across slices, and continuous monitoring.

generative

The sentence describes an AI system that creates new, original content (for example, text, images, audio, code) by learning patterns from large datasets. That is the defining characteristic of generative AI , so “generative” is the correct completion.

To clarify the contrasts: predictive AI primarily uses historical data to forecast outcomes or estimate probabilities (for example, predicting next-quarter sales, predicting equipment failure, or classifying whether a transaction is fraudulent). It focuses on what is likely to happen or which category something belongs to , rather than producing novel content. Prescriptive AI goes a step further by recommending actions or decisions (for example, “increase inventory by X,” “route tickets to team Y,” “schedule maintenance next week”) often using optimization and business constraints.

Generative AI, by comparison, is focused on content synthesis . It identifies statistical patterns and relationships in training data and then generates new sequences that resemble the learned distribution while being responsive to prompts. In business use cases, that translates to drafting emails and documents, summarizing reports, generating meeting notes, creating product descriptions, producing marketing copy, and building chat-based assistants. While all three categories can “recognize patterns,” only generative AI is explicitly characterized by the ability to produce new and original content , which is what the question is testing.

Answer Area

Extracting structured data from forms and invoices: Answer: Azure Document Intelligence in Foundry Tools

Summarizing written content from business reports: Answer: Azure Language in Foundry Tools

Generating descriptive text for uploaded images: Answer: Azure Vision in Foundry Tools

These three tasks align to three different Azure AI capability families: document processing, language understanding/generation, and computer vision.

Forms and invoices are semi-structured documents where the business need is to extract specific fields (IDs, names, totals, dates) reliably into structured output. Azure Document Intelligence is designed for intelligent document processing and includes prebuilt models (such as invoices) as well as custom extraction options, making it the correct choice for structured data extraction from documents.

Summarizing written business reports is an NLP task focused on compressing long text into key points, themes, and action items. Azure Language provides language processing capabilities (including summarization features within language service capabilities), so it is the best fit for summarization scenarios.

Generating descriptive text for images (image captioning/description) is a computer vision task. Azure Vision can analyze uploaded images and return descriptions/captions and other visual insights, which directly matches the requirement to produce descriptive text from images.