# Step 2: Implementing Drift Monitoring After implementing the default baselines and running a single report, we can now check this tenant for how far they have drifted from our baseline. This report will contain all the information on how the client deviates by category, listing the user impact. This report can be shared with the client or you can use this report to evaluate if implementation will not make massive changes and continue on. Each item in drift monitoring shows you what the expected state is, and what we have found as the current state. Drift monitoring compares your tenant to the items configured in your standard **and** all Intune and Conditional Access Policies, this allows you to capture any policy that has been created outside of your baseline. ## How to communicate changes to clients Text here how to explain these changes to your clients and some example emails. ## Handling deviations Deviations can be present for multiple reasons; client wishes, client specific software. Let's explain how you can use CIPP to configure these different types of deviations. ### Types of deviations Explain the different types ### Remediation Explain one off remediation --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.cipp.app/setup/implementation-guide/your-route-to-a-secure-tenant/step-2-collecting-tenant-information.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.