Define Office 365 in the request
If the RFP says Office 365, specify whether you mean Exchange, SharePoint and Teams alone or also their identity and device controls. An assessor can review sharing settings without evaluating whether unmanaged devices can access the same information. State the decision you need across those boundaries.
Use one evaluation case
Give every bidder the same hypothetical case: a former accountant may still have finance access. Ask how they would distinguish guest identity, site permissions, sharing links and evidence of use. Compare the reasoning rather than awarding points for the longest tool list.

Ask who collects what
Require a collection plan with named responsibilities. A provider that assumes your MSP can produce every export may underestimate coordination. Ask what happens when an export is incomplete and whether the limitation appears in the report.

Request a reporting sample
Ask to see a finding with identifiers redacted. Look for enough detail to locate the setting, understand the affected population and check closure. A severity label without context can make an exception affecting one test account look identical to an organisation-wide exposure.

Separate changes from assessment
An audit does not need blanket authority to alter your tenant. Ask whether implementation is optional and who owns change approval. A remediation recommendation should describe dependencies and a safe validation step even if another provider implements it.

Score the answers
Use a three-column decision record. For each requirement, record the evidence the bidder supplied and the remaining assumption. Treat “included” without a method as unanswered. Weight the requirements that support your business decision before seeing the prices.

Agree the handover
Before signing, establish who receives sensitive evidence, how long it is retained and who answers engineering questions after delivery. Include a distinct acceptance point for the report and for any optional retest. This prevents a purchasing decision from becoming a dispute about what “complete” meant.

A scoring exercise procurement can run
Ask each provider to respond to the same fictional departure scenario in one page. A supplier says its access was removed when its guest account expired. The application owner still sees a sharing link. A strong response explains why these are different access paths and what evidence would resolve the question. It should also say what cannot be concluded from the available data.
| Bidder answer | Follow-up question | What good looks like |
|---|---|---|
| We check all guest accounts | How do you handle links independent of that identity? | Separate identity and sharing evidence. |
| We provide screenshots | Can engineering reproduce the observation? | A dated object reference and a bounded conclusion. |
| We advise on remediation | How will we know the change worked? | A negative test and a legitimate-use check. |
Published by Atlant Security. Sources, editorial policy and corrections.

