← Back to AssessSample · made-up company
Microsoft 365 Maturity Assessment · Tab & Shift EngineeringFloor 16 Technologies
Assessment report · The Scan

Microsoft 365 Maturity Assessment

Tab & Shift Engineering Ltd. · 90 people · engineering and field services

Prepared forPrepared byDateStatus
Paige Tab
Co-founder and Managing Partner
Floor 16 TechnologiesApr 24, 2026v1.0 · Issued
Scan windowEvidenceScaleFindings valid
Apr 6 to 17, 2026Automated scan and four 30-minute interviewsEight areas, scored 1 to 590 days
In this report
  1. 01Summary
  2. 02How we measured
  3. 03The eight scores
  4. 04Risks, ranked
  5. 05Findings by area
  6. 06Licensing: paid for and used
  7. 07Quick wins
  8. 08What fixing it buys
  9. 09The year, in brief
  10. 10Next step

Summary

Tab & Shift's people use Microsoft 365 every day and use it well. The content underneath them is not in order, and the first fix is a retention schedule, because nothing can be cleaned up safely without one.

41sites shared with everyone, including two HR sites
1.6 TBof content, 62% untouched in three years
38,400duplicate files, about 210 GB
27paid licenses nobody has used in 90 days
1,140links shared outside the company, 300 with no expiry
9sites with no active owner

Where things stand

Adoption is not the problem. 86 of 90 staff were active in the last 180 days. They generated about 210,000 email actions, 169,000 Teams messages and 61,000 SharePoint file actions. One Teams message in eight is posted in a channel rather than a private chat, which is better than most companies this size.

The content is. The Scan found 520,000 files and 1.6 TB across 78 SharePoint sites and 90 OneDrives. 62% of the files have not been opened or changed in three years. 38,400 are exact duplicates of a file somewhere else. There is no retention policy, no retention label and no sensitivity label anywhere in the tenant. Tab & Shift's own records policy, a 2019 PDF on the Quality site, says project records are kept for ten years after a project closes. Nothing in Microsoft 365 carries that out, and nothing stops a deletion either.

Access has been granted by convenience. 41 of the 78 sites give access to "Everyone except external users", including HR Team and HR Records 2019. The median staff account can open 29 sites. Tenant sharing allows "Anyone" links with no expiry, and 212 of them are live today, 74 of which allow editing.

AI has started ahead of the rules. Tab & Shift bought ten Copilot seats in January. Four people use them weekly and three have not been used at all. Copilot answers from whatever the person asking can open, so today it can draw on the two HR sites for anyone in the company. Two of the four people we interviewed said staff are already pasting proposal text into free chat tools.

What is already in good shape

Two of the eight areas should be left alone while the rest is fixed. Multifactor sign-in is on for every licensed account, and 61 of 104 devices are managed (security baseline, 2.9). Teams is used the way it is meant to be used (collaboration habits, 3.1). Neither needs a project. Both need the small fixes listed in their sections.

What the work looks like

Five phases over twelve months, in the order the dependencies set. Each one is priced on its own, and the first fixes need no new licensing at all. The one-page roadmap and the fix list carry the detail.

PhaseWhenWhat it doesCost range
1 · AssessApr 2026The Scan and this report. Done.$0
2 · Clean upMay to Jul 2026Retention schedule first, then archive what is stale, remove duplicates, retire dormant sites, give every site two owners.$12k to $18k
3 · Lock downJun to Sep 2026Remove the 41 "Everyone" grants, close Anyone links, publish six sensitivity labels and the retention policies.$10k to $16k
4 · BuildJul to Dec 2026A project register, expense approvals and field job sheet capture, inside SharePoint.$28k to $45k
5 · AISep 2026 to Mar 2027A boundary test, one pilot team, then the rest, and two agents for the jobs that repeat.$15k to $25k

Floor 16 did not open a document. The Scan reads settings and file details: names, sizes, dates, owners and who can see what. Every figure in this report comes from that, from the Microsoft 365 usage reports and from four 30-minute interviews.

How we measured

The Scan ran over two weeks with read-only access approved by Sam Okafor, Tab & Shift's IT coordinator. It covered every SharePoint site and OneDrive, the tenant's sharing, security and compliance settings, licensing, and 180 days of usage.

What we looked atSourceCoverage
Files and foldersFile details only: name, size, type, created, modified, owner, path520,000 files, 78 sites, 90 OneDrives
Permissions and sharingSite, library and folder permissions, sharing links, guests3,900 permission entries, 1,140 external links
Tenant settingsSharing, guest access, security defaults, Purview, app consentAs of Apr 17, 2026
ActivityMicrosoft 365 usage reports180 days to Apr 17, 2026
LicensingSubscriptions, assignment and last activity per seat99 paid seats, 6 add-on products
InterviewsFour 30-minute conversationsApr 8 to 14, 2026
InterviewedRoleWhy them
Priya ShahDirector of OperationsOwns the project list and the weekly operations meeting
Marcus ChenChief Financial OfficerExpense claims, month end, licensing spend
Luis OrtegaField Services ManagerCrews, job sheets, client site photos
Hannah BrooksEngineering ManagerStandards, drawings, project files

The scale

Each area is scored from 1 to 5 against the levels of the Microsoft 365 Maturity Model. A score of 2.0 means the practice exists and repeats in places. It does not mean it is half done.

ScoreLevelWhat it looks like
1InitialAd hoc and manual. Nobody owns it, and it depends on who is in the room.
2ManagedSome structure in some teams. It repeats, but differs from team to team.
3DefinedWritten down, owned and followed across the company. Enforcement is partly manual.
4MeasuredEnforced by configuration, measured, and reviewed on a schedule.
5OptimizingImproved continuously from the measures. Rare, and not the target here.

Three storage figures, deliberately different. 1.6 TB is the file content the Scan measured across SharePoint (1.21 TB) and OneDrive (0.39 TB). 1.68 TB is what Microsoft reports as SharePoint storage used, which adds version history and recycle bins. 1.99 TB is the licensed pool: 1 TB plus 10 GB for each of the 99 paid seats. Accounts differ the same way: 136 exist, 99 hold a paid seat, 90 are current staff.

The eight scores

Overall maturity is 2.0 out of 5 today, against a twelve-month target of 3.3. The four lowest scores are the four that decide what AI can safely see, which is why the roadmap starts there rather than with new tools.

TodayLowest: where the roadmap starts12-month target
AreaTodayLevelTargetThe reason, in one line
Records and retention1.2Initial3.0A written ten-year rule, and nothing in the tenant that applies it
Permissions and sharing1.5Initial3.541 sites open to everyone; Anyone links allowed with no expiry
AI readiness1.6Initial3.0Seats bought before the boundary; free tools in use for proposals
Governance and ownership1.8Initial3.0Anyone can create a team; 9 sites have no active owner
Information architecture2.0Managed3.5A good project numbering scheme, applied to 71% of folders
Automation2.2Managed3.5Safety forms automated; expenses, job sheets and the project list are not
Security baseline2.9Managed3.5MFA everywhere; app consent open and 9 former staff still enabled
Collaboration habits3.1Defined3.5Channels used well; files shared in chat leave with the person
Overall2.0Managed3.3

Risks, ranked

Nine risks, ordered by what they could cost Tab & Shift rather than by how technical they are. Every one is a setting or a figure the Scan measured. None is a guess about attackers.

#RiskWhat we foundWhat it could costFixed in
1HR and payroll open to the whole companyHR Team (2,300 files) and HR Records 2019 (5,600 files) grant access to everyone. The Payroll folder inside Finance is open to 26 people, 9 of them outside finance.A salary file opened by the wrong person, or surfaced by Copilot to anyone who asksClean up, week 1
2Records kept or lost without a ruleNo retention policy or label. 4,800 files deleted from SharePoint in 180 days, 1,100 of them from the Projects site. Deleted files are recoverable for 93 days, then gone.A client or court asks for a 2018 inspection record that was deleted, or one that should have beenClean up, then Lock down
3AI shows people what they were never meant to browseCopilot uses each person's own access. With 41 open sites, the median account reaches 29 sites. No labels or exclusions exist yet.Confidential content in an AI summary; a stalled rollout once it happensLock down, then AI
4Anonymous links on client content212 Anyone links live, 74 allow editing, none expire. 61 of them point into client project folders.Client photos and reports forwarded beyond the client, with no record of who opened themClean up, week 1
5Former staff can still sign in9 former staff accounts are enabled and licensed. One, a former IT contractor, can open 52 sites.Access nobody is watching, plus about $1,350 a year in seatsClean up, week 1
6Client content in free AI toolsTwo of four interviewees described proposal text pasted into free chat tools. 3 AI apps were connected by individual staff through open app consent.Client and pricing content held by a service under consumer termsLock down
7Four versions of the project list"Project List MASTER v7.xlsx" exists in four places, edited by six people. Billing works from one, operations from another.Work billed late or not at all; a weekly meeting spent reconcilingBuild
8Storage full by mid 20271.68 TB used of a 1.99 TB pool, growing about 22 GB a month. Version history is 380 GB of it.Paid extra storage, or a read-only tenant if nobody noticesClean up
9Flows that stop without telling anyone5 of 23 Power Automate flows belong to former staff. 3 have failed every run since February.A step everyone assumes is happening, is notClean up

Likelihood and impact

Numbers match the table above. The three flagged sit in the top right: likely to happen, and costly when they do.

Likelihood up the side, impact along the bottom.

Findings by area

Each area combines what we heard in the interviews with what the Scan measured, followed by what we recommend and what changes when it is done. The areas run lowest score first.

Records and retention

1.2 · Initial · target 3.0

Tab & Shift has a records policy and nothing that carries it out. The policy says project records are kept ten years after a project closes and personnel files seven years after someone leaves. Microsoft 365 has no retention policy, no retention label and no hold, so a deletion by anyone with edit rights is final once the recycle bin empties. Nothing old is ever removed either, which is how 62% of the content came to be three years untouched.

0retention policies or labels in the tenant
322,000files untouched for three years or more
93 dayshow long a deleted file can be recovered today

Content by age, share of 520,000 files

14%Under 1 year
24%1 to 3 years
21%3 to 5 years
41%Over 5 years

Deep Sky marks the 62% past three years: the content an archive date would move out of the working set.

What we heard

“If a client asked for the 2017 inspection records tomorrow, I think we have them. I couldn't promise.”Marcus Chen, CFO
“We never close anything. Projects just stop getting opened.”Priya Shah, Director of Operations
  • Nobody deletes old content because nobody knows what is allowed to go.

What we saw

  • No retention policies, retention labels or holds on any site, mailbox or OneDrive.
  • 322,000 files (62%) untouched for three years or more, 0.98 TB of the 1.6 TB.
  • Project Archive holds 61,000 files from 2011 to 2019, and 64 people can edit it.
  • 4,800 files deleted from SharePoint in 180 days, 1,100 from the Projects site.
  • 6 former staff mailboxes converted to shared mailboxes, with no retention on any of them.
  • No project close-out step: 212 of 340 projects are finished, and none is marked closed.
ActionWhat we recommendWhat changes
Retention scheduleOne page: record type, what starts the clock, how long, who owns it. Signed off by Marcus Chen.The rule exists before anything is archived or deleted
Retention policiesApply the schedule to project, HR and finance sites and to mailboxes.A deletion inside the period can be recovered; nothing is kept forever by accident
Archive dateAgree a cut-off (we suggest untouched since Jan 2023) and move older content to a read-only archive.62% of the content leaves the working set and the AI answer set
Project close-outA closed date on every project, which starts the ten-year clock.Retention runs from a real date, not a guess

Permissions and sharing

1.5 · Initial · target 3.5

Access at Tab & Shift has been granted for convenience and never taken back. "Everyone except external users" sits on 41 of the 78 sites, through 63 separate grants at site or library level. Tenant sharing allows Anyone links that need no sign-in and never expire. Sharing outside the company is low, so the restraint so far is people's habit rather than a setting.

41 of 78sites open to everyone in the company
212Anyone links live, 74 allowing edits
29sites the median staff account can open

Who can open the sensitive sites

Site or libraryFilesShould openCan open
HR Team2,300490
HR Records 20195,600490
Finance14,200726
Finance › Payroll1,900326
Leadership Team3,100611
Bids and Proposals › Pricing2,4001290

What we heard

“I assumed HR was locked. It's HR.”Priya Shah, Director of Operations
“Payroll exports go into a folder in Finance. I don't know who else can see Finance.”Marcus Chen, CFO
  • Crews send client site photos by link because attachments bounce. Nobody revisits the links afterwards.

What we saw

  • 63 "Everyone except external users" grants across 41 sites.
  • 1,140 links shared outside the company; 300 have no expiry.
  • 212 Anyone links, 74 allowing edits, 61 pointing into client project folders.
  • 18 guest accounts; 7 have not signed in for 12 months.
  • 61 libraries with their own permissions, set by exception rather than design.
  • Widest reach: 52 sites, held by a former IT contractor's account that is still enabled.
ActionWhat we recommendWhat changes
Remove EveryoneReplace the 63 grants with named groups, HR and Finance first.HR and payroll open to the people who run them, and to AI only for them
Sharing policyTurn off Anyone links. Guest links expire in 30 days.The anonymous path closes, at no licensing cost
Revoke live linksRemove the 212 Anyone links, the 74 edit links first; re-share deliberately where still needed.Client content stops traveling without a record
Guest reviewRemove the 7 inactive guests; set guest access to expire.External access reflects live relationships
Owner attestationSite owners confirm membership twice a year.Access stays right after the cleanup

AI readiness

1.6 · Initial · target 3.0

AI use has started ahead of AI rules. Copilot, Claude and ChatGPT all answer from what the person asking can open, so the permission picture above is the AI picture. Today a field technician's Copilot can draw on HR Team, and 62% of what any answer draws on is three years old or more. None of that is the tool's fault. It is showing Tab & Shift a permissions problem it already had.

4 of 10Copilot seats used weekly; 3 never used
90staff whose Copilot could reach HR files today
0sensitivity labels to say what AI may use

What we heard

“People are pasting proposals into the free version of ChatGPT. I'd rather give them something safe.”Priya Shah, Director of Operations
“We bought ten Copilot seats because the reseller had a deal. I think four people use it.”Marcus Chen, CFO
  • Engineering wants AI to check draft reports against Tab & Shift's own standards before review.

What we saw

  • 10 Microsoft 365 Copilot seats: 4 used weekly, 3 occasionally, 3 not in 90 days.
  • No sensitivity labels, no data loss prevention policy, no site exclusions.
  • The Copilot seats include SharePoint Advanced Management, which provides restricted content discovery and data access reports. Neither is switched on.
  • 3 AI apps connected to staff accounts through open user consent.
  • About 3,400 current, owned documents (standards, procedures, templates, approved proposals) are good material for AI to draw on.
ActionWhat we recommendWhat changes
Hold new seatsReassign the 3 unused Copilot seats; buy nothing until a pilot shows who uses it.Spend follows use
Set the boundaryLabels, Everyone removed, restricted content discovery on HR, finance and leadership sites, then a boundary test.AI can be switched on without surprises
Approved toolsName the tools staff may use for company content and restrict app consent.Proposal text stops leaving through free tools
One pilot teamBids and Proposals first, on real work, measured at 30 and 60 days.Evidence before company-wide spend
Tool per jobChoose Copilot, Claude, ChatGPT or Azure AI Foundry for each job rather than one for everything.Each team gets the tool that fits its work

Governance and ownership

1.8 · Initial · target 3.0

Anyone at Tab & Shift can create a team, and many have. Sites outlive their owners: when someone leaves, their account is turned off but nobody looks at what they owned. There is no naming standard, no expiry and no record of a review.

9sites with no active owner
31sites with a single owner
0access reviews on record

What we heard

“When someone leaves, IT turns off their email. I don't think anyone looks at what they owned.”Priya Shah, Director of Operations
  • New teams are created by whoever needs one first, often per client, sometimes per meeting.

What we saw

  • 52 teams, 11 created in the last six months, 4 named "test" or "demo".
  • 9 sites whose only owners have left; 31 with one owner.
  • 26 sites with no change in 12 months; 8 more are duplicates or tests.
  • Group expiry and naming policies off.
  • 5 of 23 flows owned by former staff.
ActionWhat we recommendWhat changes
Two owners per siteName two owners for every site that stays.Someone answers for every site
Retire dormant sitesArchive or retire 34 sites with owner sign-off: 26 dormant, 8 tests and duplicates.78 sites become 44
Request, not createNew teams by a short request form, built from a template with a standard name.Sprawl stops at the source
Leaver checklistAccounts, licenses, owned sites, OneDrive and flows, every time.Nothing is orphaned when someone leaves
Quarterly reviewThirty minutes: new sites, owners, guests, links.Governance becomes a habit, not a project

Information architecture

2.0 · Managed · target 3.5

78 flat sites with no hub and no shared navigation. Most project work lives in one Projects site with 6,800 folders, each shaped by whoever created it. The good news is a project number, TS-YY-NNN, that Tab & Shift already uses on 71% of project folders. It is a sound scheme. It has just never been required.

0hub sites connecting 78 sites
71%of project folders already carry a TS-YY-NNN number
2,900file paths over 400 characters

What we heard

“I don't know which version of the standard drawing is current. I ask whoever has been here longest.”Hannah Brooks, Engineering Manager
“Every project folder looks different. Depends who set it up.”Luis Ortega, Field Services Manager

What we saw

  • Projects site: 214,000 files, 6,800 folders, nesting to 14 levels.
  • 242 of 340 project folders start with a TS-YY-NNN number.
  • Engineering Standards exists in three sites, with different contents.
  • No custom metadata column is filled in anywhere.
  • 2,900 paths over 400 characters, which break sync and moves.
ActionWhat we recommendWhat changes
Three hubsProjects, Engineering and Corporate, with shared navigation.Browsing works as well as search
One project standardThe same folders and the TS-YY-NNN number on every project.Any project looks like every other one
One home for standardsMerge the three Engineering Standards copies, with an owner.There is one current version
Fix long pathsShorten the 2,900 paths during the archive move.Sync and moves stop failing silently

Automation

2.2 · Managed · target 3.5

Tab & Shift has automated the easy thing well: safety observations go from a form on a phone into a list, 410 of them in 180 days. The processes that cost the most hours still run on email and spreadsheets: expense claims, field job sheets and the project list.

240expense claims a month, 9 days median to pay
1,100job sheets a month arriving as photos by email
4copies of the project list in use

What we heard

“The crews photograph the job sheet and email it. Someone types it into billing. Sometimes twice.”Luis Ortega, Field Services Manager
“I sign expense claims I can't see the receipts for. Month end takes six days, and two of them are chasing job sheets.”Marcus Chen, CFO
“Every Monday someone rebuilds the project list from three versions.”Priya Shah, Director of Operations

What we saw

  • Expense claims: an Excel template by email, 240 a month, receipts on paper.
  • The jobs mailbox receives 1,100 messages a month with photo attachments.
  • Project List MASTER v7.xlsx: 340 rows, four copies, edited by six people.
  • 23 flows; the safety form flow is the only one used company wide.
  • 3 flows owned by former staff have failed every run since February.
ActionWhat we recommendWhat changes
Project registerOne SharePoint list with a custom view replaces the spreadsheet; billing and operations read the same rows.The Monday rebuild stops
Expense approvalsA claim with a receipt photo, routed by rule to the right approver, with the record kept.Days to pay drop from 9 toward 3
Job sheet captureA form on the crew's phone writes to the register and produces the billing export.Nobody retypes a job sheet
Flow ownershipMove business flows to a service account with a named owner.Flows survive the person who built them

Security baseline

2.9 · Managed · target 3.5

Better than most companies this size. Security defaults turn on multifactor sign-in for every account, and the 27 Business Premium seats bring device management and sign-in rules that are partly in use. The gaps are specific and cheap to close.

100%of licensed accounts with multifactor sign-in
61 of 104laptops and phones managed
14third-party apps connected by staff, 3 of them AI tools

What we heard

  • Field tablets are shared between crew members and signed in as one account.
  • The managed service provider handles laptops; nobody owns phone and tablet policy.

What we saw

  • Security defaults on; no Conditional Access policies, though 27 seats include them.
  • Users may consent to third-party apps without review.
  • 9 former staff accounts enabled and licensed.
  • 6 shared field tablets signed in as a single account.
ActionWhat we recommendWhat changes
Restrict app consentAdmin approval for new apps; review the 14 already connected.No AI tool connects without a decision
Former staffDisable and delicense the 9 accounts today.Nine sign-in paths close; about $1,350 a year saved
Shared tabletsShared device mode, or one sign-in per crew member.Field actions trace to a person

Collaboration habits

3.1 · Defined · target 3.5

The strongest area. Teams is in daily use by 86 of 90 staff, project channels carry real work, and project reviews are recorded. The one gap matters for everything else: files dropped into a chat are stored in the sender's OneDrive, so the record of the work leaves with the person.

86 of 90staff active in Teams in 180 days
1 in 8messages posted in a channel, not a chat
136,000files in OneDrive, outside any site rule

What we heard

“Project chat works. Finding the file from the chat three months later doesn't.”Hannah Brooks, Engineering Manager

What we saw

  • 148,000 chat messages and 21,000 channel posts in 180 days.
  • 4,100 meetings, 610 recorded.
  • 22% of OneDrive files are shared with someone else, a sign they belong on a site.
ActionWhat we recommendWhat changes
Links, not attachmentsShare from the project site; one short note to all staff.Files stay with the project
Move shared OneDrive workOwners move shared project files to the project site, starting with leavers.Records survive departures
Leave the rest aloneChannels and recorded reviews work. No project needed.Effort goes where the scores are low

Licensing: paid for and used

27 paid licenses have not been used in 90 days. At list prices that is about $6,200 a year. None of the cleanup or lock down work needs a new license for the 27 Business Premium users. Whether the other 63 staff move up from Business Standard is a decision for the lock down phase, covered in the label set.

LicenseSeatsUnused 90 daysAnnual cost of unusedRecommendation
Microsoft 365 Business Standard729$1,350Remove from former staff
Microsoft 365 Business Premium270$0Keep
Microsoft 365 Copilot103$1,080Reassign to the pilot team
Project Plan 366$2,160Cancel at renewal; the register replaces it
Visio Plan 255$900Cancel at renewal
Power BI Pro44$672Cancel, or keep two for the register reports
Total12427$6,162

Scenario list prices, annual commitment. Your agreement and discounts will differ; your reseller confirms before anything is canceled.

Quick wins

Ten fixes that need no licensing, no project and no outside help. Together they take about three working days, and Tab & Shift's IT coordinator can do most of them. They close the most exposed risks before the roadmap starts.

#Quick winEffortWhoWhat it changes
1Turn off Anyone links; guest links expire in 30 days1 hourSam OkaforThe anonymous path closes for new links
2Remove Everyone from HR Team and HR Records 20191 hourSam Okafor, HRHR files open to HR only
3Disable and delicense 9 former staff accounts2 hoursSam OkaforNine sign-ins closed, $1,350 a year
4Revoke the 74 Anyone links that allow editingHalf a daySam OkaforClient files stop being editable by strangers
5Restrict user consent to third-party apps1 hourSam OkaforNo unreviewed AI app connects
6Reassign the 3 unused Copilot seats30 minutesPriya ShahPaid seats in use
7Name owners for the 9 ownerless sites and a second owner for 31 moreHalf a dayPriya ShahEvery site has someone who answers
8Remove the 7 guests inactive for 12 months1 hourSam OkaforExternal access matches live work
9Move the 5 flows owned by former staffHalf a daySam OkaforThree failing flows run again
10Send the "links, not attachments" note1 hourPriya ShahFiles stay with the project

What fixing it buys

Every figure on the left was measured by the Scan. Every figure on the right is what the roadmap delivers when the named phase is done.

MeasureTodayAfterPhase
Sites open to everyone410Lock down
Anyone links live2120Clean up
Files in the working set520,000about 160,000Clean up
SharePoint storage used1.68 TBabout 0.8 TBClean up
Sites, each with two owners38 of 7844 of 44Clean up
Content under a retention rule0%100% of project, HR and financeLock down
Unused paid licenses270Clean up
Copies of the project list41 registerBuild
Expense claim to payment, median9 days3 daysBuild
Copilot seats used weekly4 of 1010 of 10 before any are addedAI
Overall maturity2.03.3All five

The year, in brief

Lock down is the phase that matters most: it is the one people skip, and it decides what AI can find. Build runs alongside it because the register and approvals do not depend on labels.

DoneThe phase that mattersPlanned, not startedNot firm yet

Costs and the reason for each step are on the one-page roadmap.

Next step

Review the findings, confirm the priorities, choose the phases. A 60-minute working session with Priya Shah and Marcus Chen to agree the archive date, the order of the first fixes and which phases Tab & Shift wants priced. Floor 16 then provides a fixed price for each phase chosen. Many companies do the quick wins themselves first, and the report is theirs to keep either way.

DecisionWhoNeeded by
Archive date (we suggest untouched since Jan 2023)Priya Shah, Marcus ChenBefore clean up starts
Retention schedule sign-offMarcus ChenClean up, week 2
Business Premium for the 63 Business Standard staff, or notMarcus ChenBefore lock down
Pilot team for AIPriya ShahBefore the AI phase

The Scan and this report cost Tab & Shift nothing. Findings reflect the tenant as of Apr 17, 2026, and are valid for 90 days. Identity, endpoint and network configuration were reviewed only as far as Microsoft 365 settings show them.

Sample on a made-up company. Tab & Shift Engineering Ltd. and everyone named in this report are fictional. Figures are scenario numbers, rounded. Real engagements use the client's own tenant data.