Architecture & Security
Design Workshop
Two hours live in your Microsoft 365 tenant with a Microsoft-Authorized engineer. You leave with seven items, and a clause that owes them to you.
Late by one day and the €499 comes back in full, as written in the Refund Policy. Credited against implementation booked within 90 days, on the terms in the same section. Card or Maltese VAT-compliant B2B invoice, 14-day terms on request.
Seven items, and a clause that owes them to you.
Every item is written to be handed to your own team, or to your next vendor, on the day it lands. Two of them are here because the second hour of the session has to produce something you can send to somebody else.
- Written architecture document
- Current state, target architecture and migration path, written within 5 business days. Built to be handed to your internal team or any other vendor.
- Microsoft 365 security gap analysis
- Your agreed security and regulatory control families mapped against the current tenant posture. Critical gaps carry effort tags. Controls use stable ITS-M365 identifiers and public Microsoft, NIST, ENISA and EU sources.
- Azure landing-zone sketch and Terraform starter
- Phased deployment plan with timelines and cost estimates, plus the Terraform starter skeleton committed to your repository. Optional: it is dropped for the time back if your estate has no Azure in it.
- Copilot gate record
- Each gate item recorded as met, not met, out of scope or not readable, with the admin surface or Graph endpoint the answer was read from and the UTC minute it was read. Where an item was not readable the record says so and why, because an unread setting written down as met is worse than no record. Then the order the failed items have to be closed in, separating what your licences already cover from what they do not.
- AI and tenant evidence register
- One row for each question agreed in the session, drawn from the control responsibilities Microsoft hands back to you in its own attestation, or from a document you forward before we meet: the answer, the surface it came from, and when it was read. Questions your tenant cannot answer are listed as unanswered rather than filled in, and questions that are legal or contractual rather than technical are marked and routed out.
- Exit Kit handover pack
- Credentials map, architecture decision records, infrastructure-as-code state, operational runbooks, vendor and contract map, cost attribution map and a 90-day self-management guide. Transferable on day one. That is the point.
- 30 days of email support
- Questions about the document and about implementation planning stay open for 30 days after the session, by email.
One ITSailor eBook of your choice, Microsoft 365 Tenant Hardening or the DORA and NIS2 Roadmap, picked in the pre-session questionnaire. The pack itself is written into Refund Policy, section 01, item by item, so what is listed above is what the contract owes you.
Read a real deliverable first.
A redacted page of a gap analysis is published on this site. The control identifiers, the severities and the public sources are real and render from the same module the free scorecard uses. Only the findings are illustrative.
The control
Is Basic and other legacy authentication blocked tenant-wide?
What the document tells you to do
Block Basic and other legacy authentication tenant-wide. Review OAuth-based POP and IMAP use separately and disable unused protocols per mailbox.
landing-zone/ ├── main.tf ├── providers.tf ├── variables.tf ├── versions.tf ├── backend.tf ├── terraform.tfvars.example ├── address-space.md └── modules/
How the €499 works.
Pay once
Card checkout or a Maltese VAT-compliant B2B invoice with 14-day payment terms. €499 flat, one time.
Pack in 5 days, or refunded
The pack is due within 5 business days of session close. If it misses that window the EUR 499 is refunded in full and the documents are still yours when they land.
€499 credited to implementation
Book any ITSailor implementation engagement within 90 days of your session and the full EUR 499 is deducted from that quote.
Both terms are written down. Refund Policy, section 01, implementation credit states what the credit does and does not cover, including that it lapses at 90 days and cannot be redeemed against licensing.
Two hours, four blocks.
Each block ends in one of the written items above. Nothing in the two hours exists only as a conversation, and nothing in it is a walkthrough of what ITSailor sells.
- 0:00-0:30
Microsoft 365 Tenant Hardening Audit
Identity and Conditional Access posture, standing administrator count, device and mail authentication, read against the published ITS-M365 baseline. This is the pass the gap analysis is written from.
- 0:30-1:00
Azure Landing-zone Sketch
Phased migration plan, identity model, network topology, and a Terraform starter you can deploy. If there is no Azure in your estate this block is dropped rather than filled, and its time goes to the two blocks below. Half an hour is too much to spend on something you are not going to buy.
- 1:00-1:30
What Copilot Would Reach
First, what is already running: how many Copilot licences are assigned, what the switches governing AI in your tenant are actually set to, which agents exist and who owns them, and whether agent spend can appear without anyone buying a licence. Then what an assistant would reach, read from your sharing defaults, your sensitivity labels, your audit retention, and the Microsoft reports you started days before we met. Copilot inherits permissions rather than creating them, and where licences are assigned the index is built without an administrator asking for it. The handles are which sites stay indexed, which files a policy excludes, and who is on the sharing links, and the first of those takes the site out of its own search as well.
- 1:30-2:00
Who Answers What
Microsoft already answers part of every security questionnaire you will ever be sent, in an attestation report that costs nothing beyond the subscription you already have and that almost nobody opens. You download it on your own screen, under your own account and on the terms Microsoft attaches to it. We never hold a copy. Then we read the section at the end where Microsoft hands the rest back to you, sort it into what your tenant can answer, what only a document can answer and what nobody can, and work the first pile against your tenant for as long as the half hour lasts. You leave with the split, the register behind it, and the questions written down as unanswered rather than filled in.
Senior engineer, not a sales rep.
Michal Jatczak, solo founder of ITSailor. Years inside regulated, audit-heavy operations, the kind of environment where auditors actually open the logs and the security clock is always running.
“€499 doesn't buy you another ‘digital transformation’ deck. It buys you a deployable architecture plan for your Cloud, Microsoft 365 and AI automation stack. Plus an Exit Kit that means you keep full Sovereign Mastery over your operation.”
Two registers, each open to you without asking us. The 5-day delivery term and the implementation credit are ours, not a register's, and both are in the clause.
Three engagements, measured.
Measured on real tenants in the founder's prior operating roles, not ITSailor client engagements.
A regulated operator moved off unmanaged BYOD and manual laptop setup to enforceable device compliance, with Intune, BitLocker and Conditional Access.
Measured against that operator's own device estate, which was unmanaged before the rollout. The device count is not published.
Where the 30-day figure comes fromRepeat Tier-1 access requests dropped from a 14-hour queue to a 12-second automated flow, with Jira Service Management, n8n and a Slack approval step.
Measured against the same request class before the change, which took 14 hours. It is not an MTTR for anything else.
Where 12 seconds comes fromOffboarding became an execution log: HR-triggered session revocation, mailbox conversion, licence recovery and audit trace.
Licence spend that stopped recurring at one operator once offboarding recovered seats on its own. That estate's size and its total licence bill are not published, and this is not a rate quoted for yours.
Where the monthly figure comes fromWorkshop Q&A
Who runs the workshop?
What do I get after paying €499?
What access do you need to my tenant, and can you change anything?
Do I have to prepare anything before the session?
Can I see a real deliverable before I buy?
How does the €499 implementation credit work?
What happens if the deliverable pack is late?
What is the Exit Kit?
Is this a sales pitch for your services?
If I buy licences through you, am I locked in?
Can we pay by invoice instead of card?
What is the difference between the free scan and the paid workshop?
Take the templates instead.
Free packs from the same delivery repository the workshop draws on. Delivered by email, no payment.
Microsoft 365 Audit Workpapers
Security checklist, permission audit and gap analysis templates. Controls carry their ITS-M365 ID, profile, public source and required evidence.
Claude Code Starter Kit for IT Ops
7 specialist agents, 5 guided skills, a CLAUDE.md template and a one-page safety contract. Read-only by default.
AI Readiness Scan
A free 18-question self-assessment across six dimensions. Scores your readiness before you spend a euro.
Stop renting permission to operate.
Start owning your architecture.
€499. Two hours live in your tenant. The seven-item pack within 5 business days. You own everything that gets built.
Every session is run live by the founder. What the fee owes you, what happens if it is late, and what the credit does and does not cover are all in Refund Policy, section 01.