Scoped IT engineering / Justin Tahai

Microsoft 365, Azure & identity projects

Make your Microsoft environment work as intended.

North Berwick, Maine · Remote and onsite work by arrangement.

The problem

Start with what needs to work.

Access, licensing and configuration changes often span Microsoft 365, Azure, Active Directory and Group Policy. A change in one place needs to be checked against the systems and people it affects.

What the engagement can cover

Microsoft 365 and Azure configuration; identity and access; licensing; Active Directory and Group Policy changes. Work starts with your requirements and the environment already in place.

The deliverable

Configured systems and access, tested against the agreed requirements, with the change and verification documented.

From investigation to completion

Define. Implement. Verify.

  1. 01

    Describe the work

    Describe the users, systems and intended access or configuration outcome.

  2. 02

    Agree on the scope

    Agree on scope, access requirements, pricing and the checks that define completion.

  3. 03

    Verify the result

    Implement and test the agreed change, then document what changed and how it was verified.

Relevant built engineering

The same requirement-led approach underpins the role-aware access and client visibility in TAHAI IT Docs and the tenant-scoped workflows in TAHAI PSA. These are examples of built product engineering, rather than claims of client results.

See the product engineering →

One-off resolution / Defined projects / Project completion

Describe the result you need.

Scope, deliverables, access requirements and pricing are agreed before work begins. Additional work is agreed separately. No managed-service contracts or recurring monitoring plans.

Related project work