PRACTICAL WORK / TOLUWA STEPHEN ADEBAYO
Windows & Microsoft 365 support
A complete sample ticket, diagnostic decision path, customer updates and closure criteria.
Demonstration sample • Synthetic scenario • Prepared with AI assistance for this portfolio; not a client deliverable or a record of a completed incident.
01 / WORK SAMPLE
Diagnose before changing
Scenario: a remote finance user can open an Excel file in the browser but receives “Access denied” in the desktop workflow. A reporting deadline is in two hours. All names, times and observations below are fictional.
Service record
| Field | Example entry |
|---|---|
| Ticket / priority | DEMO-1042 / High: one deadline-sensitive user; browser workaround available |
| Scope | One user, one shared workbook; no wider outage reported |
| Initial evidence | Browser opens the file with the work account; desktop shows another signed-in identity |
| First decision | Confirm account mismatch before changing permissions |
| Owner / next update | Assigned support analyst / 09:30 WAT |
Investigation sequence
- Confirm the exact file URL, error text, application version, affected account and recent changes. Ask whether the user needs view or edit access.
- Check whether colleagues are affected and whether Microsoft 365 service health shows a relevant incident. Confirm the user is using the approved work identity.
- Compare browser and desktop behaviour with the same account and file. Review effective file/folder/site access only with authorised administration rights.
- In this scenario, the browser succeeds and the desktop uses a different account. Agree a safe point to save and close work, then switch the desktop application to the correct work account.
- Retest the original task. Do not broaden permissions or use public sharing as a shortcut. If the same-account failure persists, capture sanitised evidence and escalate.
Customer update
“Thanks for showing me the error. The file opens in your browser, so you have a way to continue while I check the desktop sign-in. I’ll update you by 9:30, even if the investigation is still in progress.”
02 / WORK SAMPLE
Document the result and close well
Illustrative continuation: the account mismatch is corrected with the user present. This is a synthetic outcome, not a claim about a real client incident.
Resolution log
| Time (WAT) | Observation / action |
|---|---|
| 09:05 | Confirmed reporting deadline and browser workaround; agreed remote session. |
| 09:12 | Compared signed-in identities; desktop account differed from the authorised browser identity. |
| 09:20 | User saved work and signed in to the correct desktop work account. No permission changes made. |
| 09:27 | User opened, edited and saved a test change; confirmed it appeared in the browser. |
| 09:30 | Sent closure summary, documented evidence and asked user to report any recurrence. |
Closure criteria
- The original workbook opens under the intended work identity.
- A permitted edit saves and is visible after reopening; existing access restrictions remain intact.
- The user confirms the original reporting task can continue.
- Record scope, diagnosis, action, verification, residual risk and follow-up in the ticket.
Escalation package
If unresolved: provide the business impact, exact error, timestamp/timezone, affected workload and account type, relevant service-health reference, same-account test results and steps already taken. Exclude passwords, access tokens and document contents.
Companion case: Outlook cannot connect
Establish whether the fault affects one desktop client or several users. Check service health and browser access. Compare identity, connectivity and recent changes before repairing the client. Preserve local-only data before a profile rebuild; do not reset MFA or remove a mailbox as a first response.
Reference
Microsoft guidance: service health and sharing permissions. Links are provided in the online sample; exact administration options depend on the tenant and application version.