A clear choice starts
with a clear scope.
Compare the business question, evidence and planned deliverable before choosing a review. Your existing IT provider can remain involved.
Compare the planned work
Security assessment
A defined evidence review across the agreed business accounts, device sample and recovery arrangements.
Read the scope ↗Who can access our workspace?Microsoft 365 review
An agreed configuration and evidence review focused on sign-in, privileged access and collaboration settings.
Read the scope ↗What can we restore, and who owns it?Recovery readiness
A review of backup coverage, restore-test records and the responsibilities behind agreed critical workflows.
Read the scope ↗Compare the boundaries.
Choose the right discussion.
On a narrow screen, scroll the comparison horizontally. Each service also has its own readable scope page above.
| Question | Security assessment | Microsoft 365 review | Recovery readiness |
|---|---|---|---|
| Main decision | Which agreed issues deserve attention first? | Which access or collaboration settings need follow-up? | What does the recovery evidence support? |
| Evidence to agree | Systems, asset sample, configuration and existing records. | Tenant, workloads, account roles, settings and relevant exceptions. | Critical workflows, coverage records, test results and provider responsibilities. |
| Planned output | Findings register, priorities, next owners and a readout. | Access observations, unresolved questions and scoped improvement priorities. | Coverage and responsibility map, evidence gaps and readiness actions. |
| Changes included? | No automatic implementation; changes are separately authorized. | Review first; production changes require their own scope and testing. | No live restore or failover test by default; tests need separate authorization. |
| Pricing and timing | Agreed after technical scope and capacity validation. | Depend on the actual environment, evidence and agreed work. | Depend on coverage, systems, available evidence and any separate testing. |
| Ongoing monitoring? | Not included. | Not included. | Not included. |
What all three
have in common.
A named business owner, an authorized technical contact and a written boundary before evidence collection. Findings should separate what was observed from what remains unknown, then identify who owns the next decision.
These are planned reviews, not a claim that CX provides continuous monitoring, emergency response or compliance certification. Services are preparing for launch.
See an illustrative assessment output ↗Still unsure?
Use the starting-point guide to match your concern with a useful first discussion. A questionnaire, a recovery concern and a broad security review can require different evidence.
Find your starting point ↗A defined next step
Start with your question.
Introduce your business, your IT arrangement and the decision you need to make. We discuss fit and scope before requesting evidence.
Preparing for launch. Client work requires finalized onboarding and a written agreement. No passwords or sensitive records in an introductory email.