Study guide

4.1 Business Requirements for Grounding Solutions

Microsoft Certified: AI Transformation Leader Exam AB-731

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

0.1 Current AB-731 Exam Facts 0.2 Audience Profile and the July 22, 2026 Blueprint 0.3 Independent Study Path for AB-731

2 Generative AI Foundations

1.1 Generative AI Versus Other Types of AI 1.2 Select a Generative AI Solution for a Business Need 1.3 Pretrained Versus Fine-Tuned Models

3 Cost, Risks, and Business Value

2.1 Tokens and ROI Cost Drivers 2.2 Fabrications, Reliability, and Bias 2.3 Scalability, Automation, and When Generative AI Adds Value

4 Prompt Engineering

3.1 Impact of Prompt Engineering 3.2 Prompt Engineering Techniques

5 Grounding, RAG, and Data

4.1 Business Requirements for Grounding Solutions 4.2 Retrieval-Augmented Generation (RAG) 4.3 Data Type, Quality, and Representative Datasets

6 Secure AI and Machine Learning

5.1 Importance of Secure AI 5.2 Application, Data, and Authentication Security for AI 5.3 When Machine Learning Adds Value 5.4 Lifecycle of a Machine Learning Solution

7 Microsoft 365 Copilot and Microsoft Copilot

6.1 Map Business Processes and Use Cases to Copilot 6.2 Differences in Capabilities Between Versions of Copilot 6.3 Microsoft 365 Copilot Chat on Web and Mobile 6.4 Copilot in Microsoft 365 Apps

8 Copilot Studio, Microsoft Graph, and Integrated AI

7.1 Microsoft Copilot Studio Capabilities 7.2 Microsoft Graph Capabilities 7.3 Integrated Microsoft AI, Risk Mitigation, and Safety

9 Agents, Extensibility, and Stack Mapping

8.1 Map Processes to Microsoft AI Apps and Services 8.2 When to Use Researcher or Analyst in Copilot 8.3 Build, Buy, or Extend Copilot

10 Microsoft Foundry and Foundry Tools

9.1 Map Business Processes to Foundry Tools 9.2 Azure Vision, Azure AI Search, and Microsoft Foundry 9.3 Match an AI Model to a Business Need 9.4 Scalability and Security Benefits of Foundry

11 Responsible AI and Governance

10.1 Importance of Responsible AI 10.2 Governance Principles for AI Use 10.3 Establish an AI Council 10.4 Microsoft Responsible AI Standards

12 Adoption Teams, Barriers, and Champions

11.1 Establish an Adoption Team 11.2 Common Barriers to AI Adoption 11.3 Establish an AI Champions Program

13 Impacts, Copilot Licensing, and Foundry Cost Models

12.1 Impacts to Data, Security, Privacy, and Cost 12.2 Copilot License Types 12.3 Foundry Tools Subscription Models

4.1 Business Requirements for Grounding Solutions

Key Takeaways Explain This Topic AI

Grounding supplies trusted, permissioned, citable, fresh enterprise content at generation time instead of relying only on a closed model's public training data.

Microsoft 365 Copilot work grounding uses Microsoft Graph and the Semantic Index while honoring the signed-in user's existing view permissions; indexing does not grant new access.

Microsoft states that prompts, responses, and data accessed through Graph are not used to train the foundation large language models used by Microsoft Copilot.

A leader must require grounding before go-live when answers will be treated as operational truth or when a fabrication would create legal, safety, financial, or reputational harm.

High-stakes actions such as pay, credit, safety instructions, or binding customer promises still need human review even when the answer is grounded and cited.

Last updated: September 2026

Why grounding is a go-live decision

A grounding solution retrieves content from sources the organization trusts and requires the generated answer to rely on that content. For an AI Transformation Leader, grounding is not a developer flourish. It is the control that decides whether a fluent paragraph is usable in operations, finance, people decisions, or a customer commitment.

A closed large language model (LLM) is trained on public data that existed at training time. That training set does not include this week's pricing sheet, an unpublished policy, or yesterday's incident report. If a user asks those questions anyway, an ungrounded model can still produce a confident answer. Microsoft's retrieval-augmented generation documentation names the retrieved passages grounding data : content you provide at generation time so the model is less likely to guess. The AB-731 skill is to identify the business requirements that make that pattern safe enough to ship.

Six requirements leaders must be able to name

Treat the following as go-live criteria, not as a backlog of nice-to-haves.

Requirement Leader question What fails if you skip it

Trusted sources Which repositories are authoritative for this use case? The model cites a draft, a rumor channel, or an abandoned wiki.

Permissions Does retrieval honor the signed-in user's existing rights? A grounded answer leaks a file the user could not open in SharePoint.

Citations Can a reviewer open the source that justified the claim? Audit, legal, and frontline staff cannot verify the answer.

Freshness How stale may an indexed copy be before it is unsafe? Last quarter's policy is presented as current.

Confidentiality Which labels, regions, and retention rules travel with the content? Highly confidential text is copied into a broad index or a chat transcript.

Human review for high stakes Which outputs must a person approve before anyone acts? An automated answer changes pay, credit, safety, or a binding customer promise.

Trusted sources are a governance choice. A help-desk agent might be allowed to use the published knowledge base and the current product handbook, and nothing else. A finance assistant might be limited to the signed close package and the controller's desktop procedures. Leaders name the source systems, the owners, and the exclusion list: payroll sites, legal-hold libraries, merger rooms, and personal OneDrive dumps that were never meant to be organizational truth.

Permissions are not the same as "the file lives in our tenant." Microsoft 365 Copilot work grounding uses Microsoft Graph as the permissioned map of email, files, chats, calendar, meetings, and contacts. Graph honors the same identity-based access boundary as the rest of Microsoft 365. If the user cannot view a SharePoint site, a Teams channel, or a mailbox, Copilot's grounding process must not retrieve that content either. Indexing does not mint new rights. The Semantic Index , which Microsoft enables for paid Copilot licenses, still respects role-based access and whether a SharePoint site remains searchable. Graph API shapes belong in a later chapter. The leader takeaway here is that work grounding is permission-trimmed retrieval, not a tenant-wide dump into every licensed seat.

Citations turn grounding into something a human can challenge. Microsoft Foundry's RAG pattern expects responses that can point back to source titles, URLs, or file names stored on the index. Without citations, a grounded system still looks like a black box in an audit.

Freshness is a service-level choice. Semantic Index updates for Copilot are frequent for many mailbox and SharePoint file types, but a custom Azure AI Search index is only as current as your ingestion job. Leaders ask whether a daily rebuild is enough, or whether this process needs a near-real-time push after each policy publish. Stale grounding is still grounding. It is just grounding on the wrong world.

Confidentiality includes Microsoft Purview sensitivity labels and Information Rights Management. Copilot honors usage rights granted to the user. If a file is encrypted and the user lacks rights, it must not appear as grounding. Custom RAG copies that ignore labels create a second, weaker permission system sitting beside the real one.

Human review for high stakes is the last brake. High stakes include compensation, hiring, credit, clinical or safety instructions, regulatory filings, and customer-facing legal language. Microsoft's Copilot extensibility guidance is explicit that agents connected to untrusted sources or sensitive operations should not complete those operations without careful human intervention. A leader who cannot name the human-in-the-loop step has not finished the grounding design.

Loading diagram... Work grounding versus ungrounded or web-only answers

Grounding versus ungrounded or web-only answers

Ungrounded generation uses only the model's parameters, plus whatever the prompt happens to contain. Web-only answers add public search. When web search is enabled, Microsoft Copilot can derive search terms from the user's prompt and send a query to the Bing Search service. That path can improve general knowledge. It does not know your unpublished policy, and it does not inherit your SharePoint permissions. Mixing web snippets with work data without a written rule is how confidential facts leak into a public-looking answer, or how a public blog is treated as company policy.

Work grounding is the opposite pattern: retrieve from Graph, or from an approved enterprise index, generate with that context, and show citations. Web search, if the organization allows it, is an explicit extra. It is not a substitute for work grounding.

Microsoft also states that prompts, responses, and data accessed through Graph are not used to train the foundation LLMs used by Microsoft Copilot. That fact matters in an executive conversation, but it does not replace permissions, citations, or human review. "Microsoft will not train on our prompts" is not the same statement as "this answer is grounded in the current policy the user is allowed to see."

When a leader must require grounding before go-live

Require grounding before production when any of the following is true:

The answer will be treated as operational truth: policy, price, entitlement, configuration, or a script a frontline worker will follow.

A fabrication would create legal, safety, financial, or reputational harm.

Reviewers, auditors, or regulators must see sources.

The knowledge is confidential, labeled, or permissioned across groups.

The facts change faster than the model's training cutoff.

A consumer-style chat that brainstorms marketing slogans from public brand voice might ship without enterprise grounding. A controller's close assistant, an HR policy bot, or a customer-entitlement agent must not.

In practice: An operations vice president wants a floor bot that tells associates the current refund rule. Legal will not accept "the model is very accurate." The VP's go-live list is the official policy library as the only source, citations on every answer, SharePoint permissions preserved, index refresh after each policy publish, confidential draft folders excluded, and a supervisor review queue when the bot recommends an exception. That list is the grounding requirement. It is not a technical remainder to be scheduled after launch.

Teaching illustration: relative go-live severity if a grounding control is missing (higher is more severe)