Stormwater management staff want a fundamentals-level picture of what influences Copilot grounding across Microsoft 365. Which fabric should they identify?

Microsoft Graph acts as the organizational data fabric that influences which organizational signals Copilot can use for grounding across Microsoft 365, subject to what the user can access. Stormwater management staff wanting a fundamentals-level picture of what influences Copilot grounding should identify Microsoft Graph. Conditional Access policies gate sign-in based on conditions like device and location; they are an access-control layer, not the underlying data fabric that connects Copilot to organizational mail, files, and other signals. Microsoft Fabric is an analytics data fabric for business intelligence workloads, not the organizational data fabric that influences which signals Copilot can use for grounding across Microsoft 365. Microsoft Dataverse supplies organizational context for Power Platform and business applications, but it does not determine which organizational mail, files, and other Microsoft 365 signals Copilot can use for grounding across Microsoft 365. Exam caveat: AB-900 asks for conceptual identification of Graph as the data fabric influencing Copilot grounding—without writing API code. Operational check: explain to stormwater staff that Copilot grounding follows Graph-connected Microsoft 365 content they can already access, and pair that explanation with permission reviews on sensitive stormwater repositories. At describe depth, Graph is the connective tissue across mail, files, calendars, and related Microsoft 365 signals that Copilot can ground on when the user already has access. Municipal IT should therefore discuss Graph conceptually when explaining grounding, then immediately return to permission hygiene on stormwater GIS notes, incident docs, and shared libraries rather than chasing fax, CDN, or printer myths.