CompTIA A+ · Operating Systems
Configuring and supporting cloud productivity suites — Microsoft 365, Google Workspace, cloud storage sync, collaboration tools, identity synchronization, and license assignment as a technician troubleshooting tool.
20 min read · Cloud-Based Productivity Tools
// CHECK YOUR KNOWLEDGE
Most organizations have moved email, document storage, and collaboration to cloud-hosted services. A technician in 2024 is more likely to be configuring a user's Outlook connection to Exchange Online or troubleshooting why someone can't access their files than touching an mail server. This lesson covers what that looks like in practice: how clients connect, how files sync, how identity works across on-premises and cloud environments, and the licensing system that controls what each user can actually access.
The two dominant cloud email platforms each host email in the vendor's cloud data centers, eliminating the need for on-premises mail servers.
Microsoft 365 / Exchange Online — Microsoft's cloud email service is Exchange Online, part of the Microsoft 365 suite. Users access it through:
Google Workspace / Gmail — Google's cloud email service is Gmail, part of Google Workspace (formerly G Suite). Users access it through:
Traditionally, configuring an email client required entering server addresses, port numbers, and security settings (IMAP/SMTP with specific ports). These settings were covered in the Core 1 Networking module — the technician's job was knowing them cold.
Modern authentication (-based sign-in) has changed how end users configure email clients. With modern auth, the user simply enters their email address and is redirected to the organization's sign-in page; the client receives a token and connects automatically — no port numbers or server addresses needed. Modern authentication is now the standard and preferred method for configuring Microsoft 365 and Google Workspace accounts in supported clients — flag this trend for verification.
Manual IMAP/SMTP configuration still exists for legacy clients and third-party applications that do not support OAuth. When a user or application cannot use modern auth, a technician must configure the server addresses, ports, and authentication settings manually.
▸ EXAM TIP
Modern authentication (OAuth) is now standard for cloud email setup. In a supported client (Outlook, Gmail app, Mail on iOS/macOS), the user enters their email address and signs in through the organization's identity provider — no IMAP server or port configuration needed. Manual IMAP/SMTP setup applies to legacy clients or applications that do not support OAuth. If a question describes a user setting up a new phone with their corporate email, modern auth sign-in is the expected method, not entering server settings manually.
When a user's email is not syncing or a client cannot connect:
services sync files between a user's device and the cloud, making files available on any signed-in device. The sync concepts were covered in the Core 1 Virtualization module — this lesson applies them specifically to the Microsoft and Google client apps.
OneDrive — Microsoft's cloud storage, integrated directly into Windows and included with Microsoft 365. Key technician-relevant behaviors:
▸ EXAM TIP
OneDrive Files On-Demand shows cloud-stored files as placeholders in File Explorer without consuming local disk space. A cloud-icon file has not been downloaded; opening it downloads it on demand. A user who sees files in File Explorer but gets an error accessing one on an airplane (no internet) is experiencing Files On-Demand behavior — the file exists only in the cloud.
Google Drive — Google's cloud storage, available via the Google Drive for Desktop app (which syncs a local folder to the cloud) or through the browser at drive.google.com. Google Drive for Desktop offers similar selective sync options: choose which Google Drive folders sync locally and which are accessed online only.
Both services allow a technician to configure which folders appear on a specific device, conserving local disk space while keeping all files accessible through the browser.
Both Microsoft 365 and Google Workspace provide a parallel suite of productivity applications. Knowing which tool belongs to which platform is a routine A+ question.
| Function | Microsoft 365 | Google Workspace | |---|---|---| | Email | Outlook / Exchange Online | Gmail | | Word processing | Word / Word Online | Google Docs | | Spreadsheets | Excel / Excel Online | Google Sheets | | Presentations | PowerPoint / PowerPoint Online | Google Slides | | Video conferencing | Microsoft Teams | Google Meet | | Instant messaging | Microsoft Teams chat | Google Chat | | Cloud storage | OneDrive | Google Drive |
Zoom is a third-party video conferencing platform used alongside or instead of Teams or Meet in many organizations — it is not part of either suite but is widely deployed.
Slack is a third-party instant messaging and channel platform, popular as an alternative to Microsoft Teams chat — particularly in technology companies and startups. Like Zoom, it is not part of Microsoft 365 or Google Workspace but is a common real-world tool.
The key capability that cloud-native versions of these tools add over traditional desktop-only software is real-time multi-user collaboration: multiple users can edit the same Google Doc, Google Sheet, or Word Online document simultaneously, seeing each other's changes live. This is the defining feature that cloud productivity suites offer over traditional desktop software.
▸ NOTE
Real-time collaboration = the cloud differentiator. Traditional desktop Word or Excel can share files, but only one person edits at a time. Google Docs, Google Sheets, Word Online, and Excel Online allow multiple users to type in the same document simultaneously, with changes visible instantly to everyone. This is the functional reason organizations adopt cloud productivity suites.
Most organizations that use Microsoft 365 or Google Workspace also have an on-premises domain — the directory their Windows workstations, , printers, and legacy applications authenticate against. Managing two separate directories (on-prem AD and the cloud directory) with separate usernames and passwords creates administrative burden and a poor user experience.
Identity synchronization solves this by copying user accounts from the on-premises directory to the cloud directory and keeping them in sync. The result is hybrid identity: one account exists in both places, and the on-premises password works for both on-prem and cloud resources.
Azure AD Connect (recently rebranded as Microsoft Entra Connect, following the broader Azure AD → Entra ID rebrand) is Microsoft's tool for this synchronization. It runs as a service on a Windows Server on the organization's network, periodically syncing user accounts, groups, and password hashes from on-premises Active Directory to Azure AD / Entra ID — flag the Entra rebrand for verification, and be prepared for exam questions that use either name.
With identity sync in place, a user signing into Microsoft 365, SharePoint Online, or Teams authenticates with their on-premises AD credentials — this is (SSO). The concept (Authentication, Authorization, Accounting) behind SSO was covered in the Core 1 Networking module; here, it surfaces as the reason a user's one login grants access across all synchronized services.
▸ EXAM TIP
Azure AD Connect / Entra Connect synchronizes on-premises Active Directory accounts to the cloud directory (Azure AD / Entra ID), enabling hybrid identity and SSO. The tool may appear on the exam under either name — both refer to the same function. Know: the sync runs on a Windows Server on-premises; password changes happen in on-premises AD and sync to the cloud (not the other way around by default in password hash sync mode).
▸ WARNING
Hybrid identity troubleshooting: on-prem first. If a user in a hybrid environment cannot log in to Microsoft 365, the problem may be in their on-premises Active Directory account — an expired on-prem password, a locked account, or a sync error — even though the user is trying to access a cloud service. Check on-prem AD account status before assuming a Microsoft 365 issue.
Access to cloud productivity features is controlled by license assignment. In Microsoft 365 and Google Workspace, every user account is assigned a license that determines which applications and features are available to that account.
Microsoft 365 licenses are assigned per user in the Microsoft 365 admin center. License tiers control feature access — as an illustrative example (exact tier names vary and are not exam-tested verbatim):
Google Workspace licenses are similarly assigned per user in the Google Admin console, with tiers controlling access to advanced features like extended storage, enhanced security controls, and premium video conferencing features.
Technician implication: when a user reports that an expected application or feature is unavailable, check the license assignment before diagnosing a technical fault. A user who sees only web apps when they expect desktop Office, or who cannot access a feature their colleague has, is almost certainly missing the appropriate license tier — not experiencing a software bug or configuration error.
▸ EXAM TIP
License assignment is the first troubleshooting step when a feature is missing. "A user cannot find the option to install Outlook desktop even though the organization uses Microsoft 365" → check whether the user's license includes desktop apps. "A user cannot access Google Meet's advanced features" → check their Google Workspace license tier. Licensing verification comes before investigating technical issues because it is free, immediate, and resolves the majority of feature-access complaints.
The check questions below test your ability to configure cloud productivity clients, troubleshoot access issues by checking licenses first, identify the correct tool in each suite, apply Files On-Demand behavior, and understand how identity synchronization affects hybrid environment troubleshooting.
Sign in to check your knowledge and earn XP. Sign in
