Understand the current state first
We begin with the business requirements, tenant configuration, licensing, users and devices. Existing controls and integrations matter: an access policy that looks correct in isolation can still interrupt a required workflow. The configuration plan identifies the changes, dependencies and validation steps before implementation.
Configuration with named ownership
- Identity and access: review accounts, administrative access, groups and sign-in policies; configure the agreed permissions and Conditional Access controls.
- Email and collaboration: configure the agreed Exchange Online and SharePoint Online services, with collaboration settings and access aligned to the approved data flows.
- Endpoint management: review device enrollment, configuration and compliance policies through Microsoft Intune where included in the engagement.
- Connected infrastructure: identify network and integration dependencies. Migration or infrastructure changes are included only when explicitly scoped.
- Testing and handoff: verify the agreed user and administrator workflows, document the baseline and provide the operating instructions needed by your team.
Maintain the configuration after the initial change
The original baseline will drift as users, devices and services change. Ongoing monitoring, maintenance and support can be scoped with the configuration work, including how issues are reviewed and how approved changes are recorded. The service responsibilities and coverage are agreed with your team.
Configuration supports a compliance program; it does not certify one. Where applicable, map the implementation and evidence to your NIST SP 800-171 obligations. Licensing or a particular Microsoft cloud does not by itself establish CMMC Level 2 (32 CFR Part 170) compliance.
Questions about microsoft 365 configuration
Is this only for a new tenant?
No. The work can start with an existing Microsoft 365, GCC or GCC High environment. We first establish the current configuration, requirements and dependencies, then agree the changes.
Does configuration include migration?
Migration is a separate scope decision. If data must move or a source system must be retired, the migration plan and acceptance checks are agreed explicitly.
Can you provide ongoing support?
Monitoring, maintenance and support can be included by agreement. Responsibilities, coverage and change-management expectations are defined in the engagement rather than assumed from this page.
Start with the configuration you have.
Bring a high-level view of your tenant, users, devices and the operational or compliance problem you need to solve.
Email rj@indirectit.com or call 240-331-6256.
Share a high-level summary. Use an approved secure channel for Controlled Unclassified Information (CUI), credentials and sensitive documents.