Learners work through the M365 support checklist for the four app categories that a Tier 1 healthcare IT technician handles most on managed clinical endpoints: sign-in, Outlook, Teams, and OneDrive. Every ticket follows the checklist, building the discipline of systematic troubleshooting rather than making autonomous configuration changes on the device.

Build the mental model needed to read a healthcare user's identity in Active Directory and Entra ID: what objects exist, how group-based access works, and how the relationships between users, groups, and resources shape what clinical staff can see and do in Microsoft 365 and Azure-connected systems.

Turn identity understanding into applied Tier 1 support. Learn to navigate Microsoft Entra ID to verify a healthcare user's account is active, check their group memberships, and process a standard password reset following the pre-approved checklist, the routine identity work a Tier 1 healthcare IT technician handles daily under documented workflows, without administering or engineering tenant-level settings.

Build the reasoning skills needed to reason about cloud-hosted healthcare workflows: what Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS) actually mean when clinical staff use Microsoft 365 and Microsoft Azure, and how shared responsibility divides ownership between Microsoft, the healthcare system, and the Tier 1 technician working the ticket.

Turn cloud service literacy into applied verification. Learn to run the cloud support verification checklist, confirming Microsoft service availability, checking user access paths, and identifying dependency points, so a Tier 1 technician can rule out common causes before escalating and route the ticket to the correct specialized team when escalation is needed.

Build the recognition literacy needed to look at a healthcare IT ticket and know which Azure services likely underpin it: virtual machines running clinical apps, storage holding clinical data, networking connecting clinics, and identity components authenticating clinical staff. This lets you correlate end-user symptoms to underlying services when the Service Health dashboard shows an active issue.

Turn Azure service recognition into applied Tier 1 support. Learn to check the Public Azure Status dashboard when Azure-adjacent tickets come in, communicate operational status to affected clinical staff in plain language, and warm-transfer unresolved local symptoms to Tier 2 engineering with the observed Azure Status context attached, with Azure Service Health used for subscription-specific investigation where authorized., the standard Tier 1 workflow for anything that smells like a cloud disruption.

Learn to use structured Copilot prompts to accelerate three routine Tier 1 healthcare IT support tasks—summarizing long logs, drafting ticket write-ups, and finding the right section in an admin runbook—while treating every AI-generated output as something to verify before acting on. This is not a Copilot tour: It's the durable prompting patterns and verification habits that will remain useful even as Copilot's interface evolves.

Work a coordinated multi-ticket case triggered by an overnight Azure disruption at a mid-size regional healthcare system. Your Monday queue has 5 tickets tied to sign-in, access, and communication issues that surfaced during the disruption. Some tickets trace back to the same underlying platform outage; others are local issues that happened to surface at the same time. Work each ticket using the appropriate Tier 1 procedures: review the provided mock service-health snapshot first, compare each symptom with the available platform evidence, complete the approved local verification, communicate status to affected clinical staff in plain language, and warm-transfer unresolved symptoms according to the Escalation Team Reference.