Tenant foundations
Set up or improve domains, administrator roles, identity settings and core Microsoft 365 services around an agreed design.
Microsoft cloud
Make your Microsoft cloud environment easier to secure and operate.
IrwellCore delivers scoped Microsoft 365 and Entra ID projects for organisations that need a clear outcome, accountable delivery and useful documentation at the end.
What the service covers
A focused workstream built around the required outcome.
Plan, configure and improve Microsoft cloud environments around a defined business outcome, with controlled change and a documented handover.
Identity and access
Review privileged access, MFA, Conditional Access and recovery arrangements, then implement the approved changes in controlled stages.
Migration delivery
Plan dependencies, pilot the move and coordinate users, data and cutover tasks for an agreed Microsoft cloud migration scope.
Configuration remediation
Turn a known audit finding, inherited tenant issue or inconsistent setup into a prioritised and documented project.
When to use this service
Bring a defined change, constraint or delivery gap.
A useful first conversation explains what must be different at the end, who owns the environment and what is currently blocking the team.
- A new Microsoft 365 tenant needs a clean, supportable configuration.
- An acquisition, separation or supplier change requires a tenant migration.
- Administrator access and identity controls have grown without a clear design.
- A security review has identified specific Microsoft 365 or Entra ID actions.
- The internal team or MSP needs experienced capacity for a defined cloud workstream.
Project deliverables
Useful records, not just completed tasks.
Exact deliverables are confirmed in the proposal. The aim is to leave the receiving team with enough context to operate and support what changed.
Boundaries and prerequisites
- Licensing, third-party products and migration tooling are agreed separately from delivery time.
- Production changes require customer-approved access, stakeholders and a suitable change window.
- Ongoing user support remains with your internal team or nominated MSP after handover.
- Written scope, assumptions, dependencies and exclusions
- Current-state findings and an agreed target configuration
- Implementation plan with pilot, change and rollback considerations
- Configuration record and decisions made during delivery
- Validation evidence, outstanding risks and handover notes
Delivery process
A clear route from discovery to handover.
The technical detail changes by service, but ownership and project controls stay consistent.
- 01
Scope
Define the outcome, environment, stakeholders, constraints and what a successful handover looks like.
- 02
Plan
Agree access, delivery windows, dependencies, communications and a practical change or rollout sequence.
- 03
Deliver
Complete the work in controlled stages, keeping blockers and decisions visible as the project moves.
- 04
Handover
Validate the outcome, record the configuration and transfer knowledge to the client or ongoing MSP.
Service FAQs
Questions to settle before delivery.
These answers explain common assumptions. The written proposal is the final record of what a specific project includes.
Read all general FAQsCan you work in an existing Microsoft 365 tenant?
Yes. Most projects begin with an existing environment. Discovery confirms the current configuration, access, dependencies and risks before any production change is agreed.
Do you carry out Microsoft 365 tenant migrations?
Yes, where the source, destination, data types, identities, domains and cutover responsibilities can be scoped clearly. Migration tooling and licence costs are identified separately.
Can our existing MSP stay involved?
Yes. IrwellCore can deliver a defined workstream while the MSP retains day-to-day support. Access, communications and the handback point are agreed before work starts.
Will you change security settings immediately?
Not without an agreed plan. Identity and access changes can affect every user, so dependencies, exclusions, pilot users and recovery options are considered before rollout.
Related services
Build the complete workstream without blurring ownership.
Adjacent services can be combined when their dependencies, delivery windows and acceptance checks are clear.
Start with the outcome
Discuss a microsoft cloud projects project.
Share the current environment, required outcome, timing and known constraints. The next step is a focused scope check.