Class Central is learner-supported. When you buy through links on our site, we may earn an affiliate commission.

Microsoft

Microsoft Core and Cloud Management

Microsoft via Coursera

Overview

Google, IBM & Meta Certificates – 40% Off
One Coursera Plus subscription covers most Professional Certificates on Coursera.
Unlock All Certificates
Behind every clinician's login, mailbox, and device is a layer of tenant and identity infrastructure that Tier 1 technicians need to understand, and this course builds that foundation. It is tailored for learners who have completed Microsoft 365 Platform Support (LC 2) and are ready to move from end-user application support to clinical IT backends, with no prior cloud administration experience required. You'll move beyond basic app support to the Microsoft 365 admin center, Microsoft Entra ID, and Azure backends. You'll practice provisioning users, mailboxes, and devices for clinical staff, navigating Entra ID to verify account status, check group memberships, and process routine password resets. You'll also apply shared responsibility models to healthcare workflows so you understand where Microsoft's responsibility ends and your organization's begins. By the end of the course, you'll become proficient in a practical skill healthcare IT teams rely on daily: using the Azure Service Health dashboard to identify outages, communicate status to affected end-users, and escalate unresolved local symptoms to Tier 2 engineering following standard warm-transfer procedures.

Syllabus

  • Provisioning Tasks: Execute the Clinic Workflow in the Microsoft 365 Admin Center
    • Learners work through the three routine provisioning task categories a Tier 1 healthcare IT technician handles daily in the Microsoft 365 admin center: user account provisioning, mailbox access assignment, and collaboration settings configuration. Every task follows the clinic's approved workflow, building the discipline of executing documented procedures rather than making autonomous decisions about role defaults or license bundles.
  • Device and App Support: Follow the M365 Support Checklist for Endpoint Issues
    • 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.
  • Identity Fundamentals: Read the AD Objects and Group Relationships That Shape Healthcare Access
    • 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.
  • Entra ID Navigation: Verify Status and Follow Password Reset Checklists
    • 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.
  • Cloud Fundamentals: Service Models and Shared Responsibility in Healthcare
    • 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.
  • Cloud Support Verification: Confirm Availability, Access, and Dependencies
    • 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.
  • Azure in Healthcare: Recognize the Core Services Behind Clinical Workflows
    • 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.
  • Dashboard Monitoring and Escalation: Identify Outages and Route Local Symptoms
    • 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.
  • GenAI Literacy Module: AI-Assisted Cloud Admin Diagnostics
    • 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.
  • Project Module: Identify & Escalate an Azure + M365 Disruption
    • 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.

Taught by

Microsoft

Reviews

Start your review of Microsoft Core and Cloud Management

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Someone learning on their laptop while sitting on the floor.