Describe Microsoft 365 pricing, licensing, and support practice questions

Purchase Microsoft 365 Business Premium licenses

Why it fails: Business Premium includes advanced security and device management not required, and costs more than Business Basic.

Purchase Microsoft 365 E5 licenses

Why it fails: E5 is the most expensive and includes many features not needed.

Purchase Microsoft 365 E3 licenses at full price

Why it fails: E3 is expensive and not necessary for basic email, storage, and Teams.

An active Azure subscription

Why it fails: An active Azure subscription is not a dependency for Copilot for Microsoft 365. This is a common point of confusion because Azure OpenAI services are billed through an Azure subscription, but Copilot for Microsoft 365 is a SaaS add-on attached to your Microsoft 365 tenant and licensed per user through the Microsoft 365 admin center. Microsoft Entra ID (now Microsoft Entra ID) is already included with Microsoft 365 for identity and authentication, so no separate Azure subscription is required for procurement, provisioning, or running Copilot.

A Power Automate Premium license

Why it fails: A Power Automate Premium license is not a prerequisite for Copilot for Microsoft 365. Core Copilot features, such as drafting a Word document, generating an Outlook email reply, or summarizing a Teams chat, work out of the box with no Power Automate capacity. While optional extensibility scenarios—like building a custom agent with Power Platform connectors—may invoke flows that require Power Automate licensing, those are advanced capabilities beyond the baseline Copilot service and are not needed to provision or use Copilot.

Microsoft 365 Business Basic

Why it fails: Microsoft 365 Business Basic is not an eligible base plan because it only provides Office web apps and mobile apps; it does not include the desktop versions of Word, Excel, PowerPoint, or Outlook. Copilot for Microsoft 365 depends on having those desktop client applications available, since the Copilot experience is deeply embedded in their UI (for example, 'Draft with Copilot' in Word). Even though Business Basic includes Teams and SharePoint, the absence of the full Office desktop suite is the decisive technical blocker that makes the plan unsupported.

Microsoft 365 E3

Why it fails: Microsoft 365 E3 does not include 24/7 phone support; it only provides online support. Therefore, A is incorrect.

Microsoft 365 Business Basic

Why it fails: Microsoft 365 Business Basic does not include 24/7 phone support; it only provides online support. Therefore, B is incorrect.

Microsoft 365 F3

Why it fails: Microsoft 365 F3 does not include 24/7 phone support; it only provides online support. Therefore, D is incorrect.

Microsoft Teams

Why it fails: Microsoft Teams is a collaboration client that is licensed with every Microsoft 365 enterprise plan, including both E3 and E5, so its presence does not distinguish the E5 feature set. Teams itself provides chat, meetings, calling, and app integration without requiring an E5-only license, even though some governance features are layered on by other E5 services.

Exchange Online

Why it fails: Exchange Online is the core messaging and calendaring infrastructure for Microsoft 365, and mailbox licensing for E3 and E5 is essentially the same; both plans grant a full user mailbox, Exchange Online Protection, and basic compliance tools. Since E5 does not add a fundamentally different Exchange service, Exchange Online cannot be one of the target E5-exclusive services, unlike the advanced security features in E5.

Microsoft 365 E1

Why it fails: Incorrect. Microsoft 365 E1 does not include Copilot; it requires an add-on license and E1 is not eligible for the Copilot add-on.

Microsoft 365 Business Basic

Why it fails: Incorrect. Microsoft 365 Business Basic does not include Copilot; it is not eligible for the Copilot add-on.

Microsoft 365 F3

Why it fails: Incorrect. Microsoft 365 F3 does not include Copilot; it is not eligible for the Copilot add-on.

The organization has a limited number of Teams licenses

Why it fails: This is incorrect because Teams is not licensed separately; it is one of the service plans included in Microsoft 365 E3. Group-based licensing assigns or removes the entire product SKU, and while you can disable specific service plans like Teams within an assigned license, doing so does not return any unused 'Teams license' to a pool. The organization either has E3 licenses for users or it does not — the number of Teams licenses is not a countable constraint.

The Sales department does not need collaboration features

Why it fails: Although it is plausible that a department might not require Teams collaboration capabilities, this is not a valid justification for disabling Teams in a licensing policy. Teams is tightly integrated with other Microsoft 365 apps, and removing it would not reduce costs because the E3 license fee remains the same. The decision to disable Teams typically stems from a specific technical or compliance factor, not a general lack of need.

The users in Sales are external contractors

Why it fails: External contractors are handled differently in Microsoft 365. Rather than being assigned a full E3 license through group-based licensing, external users are typically invited as B2B guest users, which use a free Microsoft Entra External ID tier and have restricted access to SharePoint, Teams, and other apps. If Sales users were true external contractors, they would never appear in a group-based licensing policy that assigns E3 licenses, making this explanation inconsistent with Microsoft's licensing model.

All E3 licenses are currently assigned to users

Why it fails: ConsumedUnits is 95, so 5 licenses are unassigned.

There are 10 unused Microsoft 365 F3 licenses

Why it fails: DESKLESSPACK is F3; ActiveUnits=50, ConsumedUnits=50, so all are used.

There are 200 unused Microsoft Power Automate Free licenses

Why it fails: FLOW_FREE has 200 active and 10 consumed, leaving 190 unused, not 200.

Microsoft 365 Business Basic with Standard support

Why it fails: Microsoft 365 Business Basic is a low-cost, entry-level plan that provides web and mobile versions of Office apps, but it does not include a support SLA guaranteeing response within one hour. With Standard support, critical incident response times are typically measured in hours, not minutes, and are defined as best-effort rather than contractual. Thus, it fails the stated sub-one-hour critical response requirement without an additional paid support agreement.

Microsoft 365 E3 with Professional Direct support

Why it fails: Microsoft 365 E3 with Professional Direct support offers enterprise-grade licensing and a support add-on with fast response, but for an organization with under 50 users this combination is disproportionately expensive. The E3 per-user license costs substantially more than Business Premium, and Professional Direct requires an additional annual fee, making it a poor cost-to-value choice. While it may technically meet the response time, the licensing is overkill and not optimized for small business needs.

Microsoft 365 E5 with Premier support

Why it fails: Microsoft 365 E5 with Premier support bundles advanced compliance and security capabilities into a premium per-user SKU, but Premier support is designed for large enterprises with dedicated account management and high-volume incident needs. The combined E5 licensing plus Premier support fees would be prohibitively expensive for a small company, and the plan's complexity is unnecessary if the sole requirement is a guaranteed critical-response time. Therefore, this option is not a practical or cost-effective solution for the company.

Purchase a standalone Microsoft Defender for Office 365 Plan 2 subscription

Why it fails: Microsoft Defender for Office 365 Plan 2 is not available as a standalone SKU; it exists only as an add-on to an eligible Microsoft 365 subscription such as E3 or E5. Since there is no standalone product to purchase, this option is factually impossible and cannot be implemented, regardless of cost or need.

Downgrade E5 users to E3 and purchase add-ons for all

Why it fails: Downgrading E5 users to E3 and then purchasing add-ons for everyone is counterproductive because E5 already includes many features beyond Defender for Office 365 Plan 2, such as advanced compliance, analytics, and additional security tools. Rebuilding those capabilities via separate add-ons would likely cost more than keeping the E5 licenses and would cause unnecessary administrative overhead and potential service disruption.

Upgrade all E3 users to E5 to include Defender for Office 365 Plan 2

Why it fails: Upgrading all E3 users to Microsoft 365 E5 is wasteful when only Defender for Office 365 Plan 2 is required, since E5 bundles numerous unrelated features like Power BI Pro, advanced eDiscovery, and additional security services. The per-user upgrade price far exceeds the cost of the Defender add-on, making this option an expensive over-provisioning that contradicts the principle of licensing only what is needed.

Microsoft 365 E1

Why it fails: E1 lacks eDiscovery and retention policies.

Microsoft 365 E5

Why it fails: E5 includes all features but is more expensive than needed.

Microsoft 365 Business Basic

Why it fails: Business Basic does not include eDiscovery and retention policies.

Microsoft 365 Business Basic

Why it fails: Microsoft 365 Business Basic is a low-cost subscription that provides Exchange Online, SharePoint, Teams, and web-based Office apps, but its included support tier is limited to online self-help and web/chat based cases. It does not include 24/7 phone support, so if the company requires direct telephone assistance for its Microsoft 365 users, this plan by itself cannot satisfy that need. Organizations needing phone support would need Business Premium or an add-on support plan.

Microsoft 365 E3 with Standard support

Why it fails: Microsoft 365 E3 is an enterprise-grade licensing plan that includes robust productivity and security features, but the 'Standard support' that is bundled with enterprise subscriptions only provides online/self-help resources and does not include phone access. The E3 plan's included support tier does not offer the 24/7 telephone incident handling that the company needs; phone support would require purchasing an additional paid support plan such as Professional Direct or Premier. Therefore, selecting E3 with its default standard support fails the stated support requirement.

Microsoft 365 E1 with Professional Direct

Why it fails: Microsoft 365 E1 is a user-license subscription focused on enterprise collaboration and communication, but it does not include any guaranteed phone support in its base price. Professional Direct is a separate support plan that must be purchased on top of E1, which means the support capability is not an inherent part of the Microsoft 365 subscription and requires an additional per-service or per-incident cost. That extra purchase makes this combination costlier and more cumbersome than simply selecting Business Premium, which already includes 24/7 phone and web support.

Purchase an additional license and assign it via the Volume Licensing Service Center

Why it fails: Purchasing an additional license is unnecessary because the organization's Microsoft 365 subscription already includes 200 licenses; the problem is that the user is not assigned an available license. The Volume Licensing Service Center (VLSC) is designed to manage volume licensing agreements and product keys, not to assign user licenses within a specific tenant. Therefore, this action would not resolve the license assignment issue and would only add unnecessary procurement overhead.

Manually assign the license in the Microsoft 365 admin center to the user

Why it fails: Manually assigning the license in the Microsoft 365 admin center would grant the user access immediately, but it is a one-time, point-in-time action that does not scale for an organization with 200 users. Any new hire or group membership change would require an administrator to individually edit license settings, which is error-prone and creates ongoing administrative overhead. In contrast, group-based licensing automatically handles assignments based on group membership, making manual assignment less efficient and less maintainable even though it is technically correct for a single user.

Use Microsoft Graph PowerShell to assign the license

Why it fails: Using Microsoft Graph PowerShell to assign the license is technically feasible, but it requires writing and executing a script with appropriate administrative permissions each time a license needs to be assigned. This method does not provide continuous automation for future users joining the group; it only assigns a license at the exact moment the script runs. For a single assignment, PowerShell is more complex than using the admin center or group-based licensing, and it bypasses the built-in license management and audit capabilities that Microsoft provides.

Microsoft 365 F3

Why it fails: F3 is for frontline workers and does not support Copilot.

Microsoft 365 E3

Why it fails: E3 does not include the necessary AI features for Copilot without additional licenses.

Microsoft 365 Business Premium

Why it fails: Business Premium does not include Copilot licensing.

Upgrade all users to Microsoft 365 E5

Why it fails: Upgrading all to E5 increases costs unnecessarily for users who don't need advanced security.

Downgrade all users to Microsoft 365 E3

Why it fails: Downgrading removes advanced security features from users who need them.

Purchase a single E5 license and share it across all users

Why it fails: Licenses cannot be shared; each user needs their own license.

Contact Microsoft Support for a temporary extension

Why it fails: Grace periods are automatically applied at the tenant level when a Microsoft 365 subscription expires; no support agent or policy can grant an additional extension beyond the standard 30-day window. Microsoft Support has no tool to override the billing lifecycle state, and requesting an extension is not a valid remediation. The correct action is to renew or relicense the subscription.

Assign a different license from another user

Why it fails: This scenario points to a subscription-level expiration, not to a per-user license assignment problem. When the subscription ends, the entire tenant loses access unless a grace period applies, so reassigning a license from another user neither restores the subscription's validity nor changes its expiration date. License assignment only controls feature access after the subscription is active.

Purchase a new subscription immediately

Why it fails: Buying a brand-new subscription, especially one on a different offer or tenant, is unnecessary and can cause data separation because the existing tenant's services are still tied to the original subscription. During the grace period, the correct step is to renew the existing subscription, which restores billing continuity and preserves all configured data, settings, and identity objects. Purchasing a new subscription also risks duplicate costs and service gaps.

Microsoft 365 F3

Why it fails: Microsoft 365 F3 is designed for frontline workers, but it bundles a broad set of services beyond Exchange Online, including Teams, SharePoint, Yammer, Power Apps, and Microsoft 365 web/mobile apps. Assigning F3 to a seasonal contractor for a limited period adds unnecessary collaboration and app services, which increases licensing cost compared to a standalone Exchange Online Kiosk mailbox.

Microsoft 365 Business Basic

Why it fails: Microsoft 365 Business Basic includes Exchange Online plus Teams, SharePoint, OneDrive, and Office web/mobile apps, though it does not include desktop Office installations. While it is a common SMB bundle, its per-user price and extra workloads are overkill for a seasonal contractor who only needs a shared-style mailbox; the Kiosk plan delivers the same mail/calendar capability at a lower cost.

Microsoft 365 Enterprise E1

Why it fails: Microsoft 365 Enterprise E1 is an enterprise-grade suite that provides Exchange Online (50 GB mailbox), Teams, SharePoint, Yammer, and advanced compliance tools such as eDiscovery and legal hold. For temporary seasonal workers who need only basic email and calendar, these enterprise security, compliance, and collaboration features are irrelevant and drive the per-user cost well above the Exchange Online Kiosk license.

Availability of phone support

Why it fails: Both plans include phone support.

Support for Mac users

Why it fails: Both plans support Mac users.

Upgrade to Microsoft 365 E3

Why it fails: More expensive and includes enterprise features not needed.

Upgrade to Microsoft 365 F3

Why it fails: F3 is for frontline workers and does not include desktop Office apps.

Purchase Exchange Online Plan 1 add-on

Why it fails: Does not include desktop Office apps.

Assign the Enterprise Mobility + Security E3 add-on to all users.

Why it fails: Enterprise Mobility + Security E3 does not include Microsoft Defender for Identity; it includes Microsoft Entra ID P1 and Intune. Defender for Identity is part of EMS E5 or available standalone. This add-on would not provide the required protection.

Enable Defender for Identity in the Microsoft 365 admin center; it is included in E3.

Why it fails: Defender for Identity is not included in Microsoft 365 E3. It requires either an E5 license or a standalone add-on. Enabling it in the admin center without proper licensing will not grant access to the service.

Upgrade all users to Microsoft 365 E5, as Defender for Identity is not available as a standalone add-on.

Why it fails: Defender for Identity is available as a standalone add-on, so upgrading to E5 is not the only option. While E5 includes it, purchasing the standalone license is a valid and often more cost-effective approach for E3 customers.

Keep E3 and add Microsoft 365 E5 Compliance add-on

Why it fails: Adding the Microsoft 365 E5 Compliance add-on to E3 licenses provides Microsoft Purview Information Protection capabilities such as sensitivity labels and data loss prevention, but it does not include Defender for Office 365 Plan 1. Email threat protection requires a separate add-on, so this option only partially satisfies the stated requirements, leaving critical security coverage missing.

Keep E3 and add Microsoft 365 E5 Security add-on

Why it fails: The Microsoft 365 E5 Security add-on bundles advanced security tools like Defender for Identity and Defender for Endpoint, but it does not include Defender for Office 365 or Microsoft Purview Information Protection. This means you would still need to purchase the Compliance add-on separately to meet the information protection requirement, making the licensing stack more complex and incomplete for the stated needs.

Keep E3 and use the Security & Compliance Center for E3

Why it fails: The Security & Compliance Center in Microsoft 365 E3 is a management portal that provides only basic compliance features like audit log search and retention policies, but it cannot unlock advanced workloads. E3 does not include the underlying service licenses for Defender for Office 365 or Microsoft Purview Information Protection, so accessing the portal does not grant these capabilities; licensing must be added separately.