Start with the evidence
Ask the assessor to work backwards. To evaluate an exclusion they may need policy assignments and representative sign-in evidence. That does not automatically require the ability to change the policy or read mailbox contents. Tie each requested capability to a specific audit question.
Choose an accountable identity
Avoid shared credentials. Identify who will use each account, who sponsors it and when access should end. Apply your normal external-access controls. If a provider cannot work within them, resolve the reason before granting an exception.

Check workload boundaries
A role that exposes directory configuration does not automatically expose all mail, endpoint or audit records. Ask for the precise role or export needed in each workload. If permission is insufficient, record the affected test rather than escalating to broad administrator access by default.

Offer a supervised alternative
For sensitive records, an authorised administrator can run a reviewed query while the assessor observes. Agree the time range, identifiers and redaction before the session. Record who produced the evidence so a later reviewer can distinguish a customer-provided extract from independent collection.

Protect the working papers
A configuration export may expose administrator identifiers, trusted locations or sensitive group names. Decide where the material can be stored and who may receive it. Agree a retention period and deletion or return procedure; the initial sales form is not the channel for raw exports.

Handle unexpected findings
Agree whom to call if the review uncovers a suspicious forwarding rule or an unfamiliar privileged application. The auditor should preserve the relevant observation and contact the authorised owner. Investigating or disabling the object may require a separate incident-response decision.

Close access deliberately
At completion, reconcile temporary accounts, group memberships and application consent against the original access list. Ask the administrator to verify removal rather than relying on a calendar reminder. Retain a brief closure record alongside the final report.

What to do when a collection request is too broad
A bidder asks for permanent Global Administrator access to simplify setup. Ask for a task-by-task alternative. An authorised customer administrator might collect one narrowly scoped export while a named assessor uses a time-bound reader role for the rest. Document the visibility lost in that arrangement. The aim is a defensible conclusion under agreed permissions, not an unexplained demand for unrestricted access.
| Request | Alternative to discuss | Evidence to retain |
|---|---|---|
| Inspect policy assignments | Named reader with relevant workload visibility | Assignment and expiry record. |
| View sensitive audit activity | Supervised, filtered customer-run search | Query scope and collection timestamp. |
| Confirm revocation | Customer checks role and group membership | Dated closure confirmation. |
Published by Atlant Security. Sources, editorial policy and corrections.

