Describe Microsoft 365 pricing, licensing, and support practice questions

Purchase Microsoft 365 Business Premium licenses

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

Purchase Microsoft 365 E5 licenses

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

Purchase Microsoft 365 E3 licenses at full price

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

Instruct the user to compress the file

Why wrong: Compressing the file with a utility like 7-Zip or WinZip may shrink it below the 25 MB threshold, but it does not alter the Exchange Online organization-wide message size limit. If the compressed file still exceeds the limit, or if the file type is already compressed (for example, MP4 or PDF), the email will still be rejected. This approach is purely a user-side workaround and does not satisfy the requirement to increase the attachment limit.

Purchase an Exchange Online Kiosk add-on

Why wrong: Purchasing an Exchange Online Kiosk add-on is unrelated to attachment size limits. The Kiosk plan is designed for lightweight shared-mailbox scenarios, offering a small 2 GB mailbox and no desktop Outlook client, so it cannot raise the 150 MB transport cap or any per-message size limit. Adding this license would incur extra cost and still leave the default 25 MB message size restriction in force, making it an entirely ineffective fix.

Have the user upload the file to OneDrive and share a link

Why wrong: Uploading the file to OneDrive and sharing a link is a practical collaboration workaround, but it does not increase the Exchange Online message size limit. When the user sends a link, the file is not transmitted through the Exchange pipeline as an attachment, so the policy is bypassed rather than changed. If the requirement is to increase the maximum allowed attachment size for email, this action fails to modify the transport configuration, even though it is a valid alternative for sharing large files.

An active Azure subscription

Why wrong: 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. Azure AD (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 wrong: 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 wrong: 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 Entra ID P1

Why wrong: While Microsoft Entra ID P1 does support password hash synchronization, it is an identity-only license and does not include Exchange Online, SharePoint Online, Teams, or other Microsoft 365 productivity workloads. Thus, a standalone P1 license cannot satisfy the organization's need for Microsoft 365 services for its mixed on-premises and cloud users.

Microsoft 365 E3

Why wrong: Microsoft 365 E3 bundles Microsoft Entra ID P1 together with the full Microsoft 365 enterprise workload licenses. This gives you password hash synchronization for hybrid identities while also providing access to Exchange Online, SharePoint Online, Teams, and the Office desktop apps, making it the only option that meets both the identity sync and productivity requirements.

Microsoft Entra ID P2

Why wrong: Microsoft Entra ID P2 includes everything in P1, such as password hash synchronization, but it adds Identity Protection and Privileged Identity Management features. These extra security capabilities are not required for the scenario, and like P1, P2 is still an identity-only license that lacks Microsoft 365 workloads, making it both overkill and insufficient.

Cancel the subscription immediately

Why wrong: Canceling the subscription immediately terminates the renewal cycle and disables all Microsoft 365 services at the end of the current billing period. After cancellation, administrators lose access to admin portals and user data may be permanently deleted after the retention period, so this action breaks service continuity rather than resolving a billing concern. You should not cancel to fix a perceived expiration issue; instead, confirm recurring billing or complete a manual payment.

Wait for the grace period to expire

Why wrong: Waiting for the grace period to expire is risky because the grace period is only a temporary state after a payment failure, typically granting limited access, such as read-only or reduced functionality, for about 30 days. If payment is not made during this time, services are fully disabled and the tenant may be marked for deletion, with data purged after a set retention window. This approach introduces avoidable downtime and potential data loss, making it an incorrect remedy for a subscription that should remain active.

Purchase an additional add-on license

Why wrong: Purchasing an additional add-on license does not extend the subscription term of the base Microsoft 365 Business Basic plan. Add-ons, such as Microsoft 365 Business Voice or Advanced Compliance, are tied to the same expiration date and billing interval as the core subscription, so they expire when the base plan expires. This option only increases the number of licensed users or features temporarily; it does not resolve the need to renew or maintain the base subscription itself.

Purchase Microsoft 365 F3 licenses

Why wrong: Microsoft 365 F3 is designed for frontline workers with a 2 GB Exchange Online mailbox and no installed Office desktop apps; instead it provides web and mobile Office apps. For temporary contractors who need a 50 GB mailbox and full Microsoft 365 web apps, F3's mailbox quota and app limitations make it unsuitable, so it is incorrect.

Purchase Microsoft 365 E5 licenses

Why wrong: Microsoft 365 E5 bundles advanced security (e.g., Defender for Office 365 P2, Purview), Power BI Pro, and enterprise telephony, with a monthly per-user cost far exceeding Business Basic. Temporary contractors only need basic email and Teams, so allocating E5 licenses wastes budget and administrative overhead; thus it's incorrect.

Purchase Microsoft 365 E3 licenses

Why wrong: Microsoft 365 E3 includes the full Office desktop suite and enterprise compliance features, but at a substantially higher monthly cost than Business Basic, and it also requires a yearly commitment when purchased monthly. Since contractors only need lightweight collaboration via web apps and Teams, E3's desktop apps and advanced capabilities exceed the requirement, making it an incorrect choice.

Microsoft Entra ID

Why wrong: Microsoft Entra ID is the identity and access management service that authenticates users and enforces conditional access policies, but it does not create or manage device compliance policies. Compliance policies that define required OS versions, BitLocker settings, or device threat levels are authored in Intune, with the resulting compliance status passed to Entra ID for access decisions. As a result, while Entra ID is essential for applying conditional access, it cannot serve as the tool to define device compliance.

Microsoft Defender for Cloud Apps

Why wrong: Microsoft Defender for Cloud Apps functions as a cloud access security broker (CASB), providing transaction monitoring, session control, and threat detection for cloud applications. It works at the application layer, evaluating user behavior and data interactions, but it has no visibility into or control over device configuration, health, or compliance posture. Therefore, it cannot be used to define or enforce device compliance policies; those require a mobile device management solution.

Microsoft Purview

Why wrong: Microsoft Purview delivers information protection and compliance capabilities, including data classification, sensitivity labels, retention policies, and data loss prevention rules. While Purview can use device signals in its policies, it does not manage devices or assess hardware and software compliance against organization baselines. Device compliance policies—such as requiring a minimum OS version or encryption—are outside Purview's scope, making it an incorrect choice for this task.

Microsoft 365 E3

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

Microsoft 365 Business Basic

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

Microsoft 365 F3

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

Microsoft Teams

Why wrong: 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 wrong: 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 wrong: 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 wrong: Incorrect. Microsoft 365 Business Basic does not include Copilot; it is not eligible for the Copilot add-on.

Microsoft 365 F3

Why wrong: 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 wrong: 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 wrong: 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 wrong: 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 wrong: ConsumedUnits is 95, so 5 licenses are unassigned.

There are 10 unused Microsoft 365 F3 licenses

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

There are 200 unused Microsoft Power Automate Free licenses

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

OneDrive for Business storage

Why wrong: OneDrive for Business storage is allocated from the SharePoint Online storage pool and is managed by Microsoft 365, not by an Azure Storage account. ARM templates deploy Azure resources like storage accounts, but OneDrive storage is a SaaS offering that cannot be provisioned or configured through an ARM template. It is scoped to a user's personal library, not tied to the Azure infrastructure that ARM templates control.

SharePoint Online storage quotas

Why wrong: SharePoint Online storage quotas are administratively assigned within the Microsoft 365 admin center and represent a shared pool provided by the service, not an Azure-resource-deployed blob store. Since ARM templates only manage Azure infrastructure, a SharePoint quota is not a deployable object in a template and has no correlation to an ARM-defined storage account. Even when SharePoint Online uses Azure for certain features, the core quota itself remains part of the Microsoft 365 service boundary.

Exchange Online mailbox limits

Why wrong: Exchange Online mailbox limits are enforced by Microsoft 365 based on license type and mailbox database settings, with no dependency on an Azure Storage account or ARM template. ARM templates cannot create or affect Exchange Online mailbox storage because the mailbox backend is entirely hidden within Microsoft's datacenter and isn't exposed to the Azure Resource Manager API. Therefore, an administrator reviewing an ARM template for storage would never intend an Exchange mailbox, as it lacks any Azure storage representation.

Microsoft 365 Business Basic

Why wrong: Microsoft 365 Business Basic is unsuitable because it offers only web and mobile versions of Office apps, not the desktop applications required for full productivity. It also lacks the enterprise compliance tools like Litigation Hold and eDiscovery (Standard) that the scenario demands, as those are included in E3. With 500 users, this plan would also force a reliance on additional licensing for features already missing.

Microsoft 365 Business Premium

Why wrong: Microsoft 365 Business Premium is limited to 300 licensed users, so it cannot accommodate a 500-user deployment. Although it includes desktop Office apps and some lightweight eDiscovery capabilities, its compliance controls are optimized for small businesses and do not provide the same governance, hold, and verification depth as E3's compliance center. At 500 users, a Business plan is not a viable legal or technical fit.

Microsoft 365 E5

Why wrong: Microsoft 365 E5 is incorrect for this scenario because it bundles advanced security and analytics features—such as Microsoft 365 Defender, advanced eDiscovery, and Power BI Pro—that go beyond the stated need for basic compliance and productivity. These extras significantly raise per-user cost without adding value for the described requirements. E3 already provides the required desktop apps and litigation hold/eDiscovery capabilities.

Extend the trial period for 30 additional days

Why wrong: Trial extensions are only available for active trials, not expired paid subscriptions; Microsoft grants a single 30-day trial extension only when the trial is still in its initial active period from the Microsoft 365 admin center's Billing > Your products page. Once a paid subscription has expired, the provisioning state is no longer trial, and an extension cannot be applied retroactively to restore a tenant that has already lost Teams access.

Wait for the subscription to automatically renew within 30 days

Why wrong: Recurring billing in Microsoft 365 is processed before the subscription end date; if payment fails or the term ends, the subscription enters a 30-day grace period and does not automatically renew itself. Merely waiting for a renewal after expiration is ineffective because no background process re-instates an expired subscription; you must either reactivate it or repurchase it. The admin must take explicit action to resume service, and this action cannot be deferred.

Purchase a new subscription and assign licenses to users

Why wrong: Purchasing a new subscription requires selecting a new plan, completing an order, and then manually assigning each product license to affected users, which is slower and more expensive because a new term starts and the previous subscription remains separate. It also risks licensing gaps if existing groups or shared mailboxes are not immediately provisioned, and it does not simply recover the expired one. The existing subscription's reactivation path is the intended recovery mechanism and eliminates these extra steps.

Keep all users on E5 but reduce the number of licenses

Why wrong: Reducing the total number of E5 licenses would remove those users from the subscription entirely, not lower the per-user cost. The users in question still need Exchange Online and the Office desktop apps, so eliminating their seats would violate the requirement. Retaining E5 for them also continues paying for advanced capabilities (Defender for Office 365, eDiscovery, Customer Lockbox) that they are unlikely to consume, leaving the per-user spend unchanged.

Switch to Microsoft 365 E1 licenses for those users

Why wrong: Microsoft 365 E1 is an enterprise-level, cloud-only subscription that includes Exchange Online, SharePoint, Teams, and web versions of Office, but it does not include the installable desktop Office applications. The requirement explicitly calls for Office desktop apps, so moving users to E1 would force them onto the web clients or require an additional Office ProPlus license, largely canceling the intended savings. While E1 also lacks E5’s security compliance tools, the disqualifying limitation here is the missing Office client.

Assign Microsoft 365 Business Basic licenses to those users

Why wrong: Microsoft 365 Business Basic is designed for small and medium businesses (up to 300 users) and includes Exchange Online and Teams but only web and mobile Office apps—no desktop Word, Excel, or PowerPoint. For a multinational enterprise with an E5 subscription, this SKU is not a valid substitute because users need desktop Office apps and the organization's scale and agreement type are beyond what Business Basic supports. Even if Office desktop apps could be added separately, mixing Business Basic into an enterprise tenancy creates licensing and management inconsistencies.

Microsoft 365 Business Basic with Standard support

Why wrong: 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 wrong: 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 wrong: 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 standalone Microsoft 365 Copilot licenses

Why wrong: Microsoft 365 Copilot has never been sold as a standalone subscription; it is a per-user add-on that must attach to an eligible base plan, such as Microsoft 365 Business Premium. Purchasing standalone licenses would be impossible because there is no such SKU in the Microsoft 365 admin center or CSP catalog. Additionally, without an eligible base plan, Copilot would have no underlying services (Exchange, SharePoint, Teams) to contextualize against. Therefore, this option is not a valid acquisition path.

Upgrade all users to Microsoft 365 E5 to get Copilot included

Why wrong: Upgrading all users from Business Premium to Microsoft 365 E5 is a major operational and financial change, yet E5 does not include Microsoft 365 Copilot. Copilot is a separate add-on that still must be licensed on top of E5 or Business Premium. The E5 upgrade adds advanced security and analytics features, but those are unrelated to Copilot entitlement. Thus, moving to E5 alone would not grant Copilot and would incur unnecessary cost.

Purchase a new Microsoft 365 E3 subscription and add Copilot

Why wrong: Purchasing a new Microsoft 365 E3 subscription and then adding Copilot would be redundant and cost-ineffective because the organization's existing Business Premium subscription already qualifies for the Copilot add-on. E3 would require the same per-user Copilot add-on license, and managing two separate base plans for the same group of users creates licensing overhead and potential duplicate assignment conflicts. The only way E3 would be justified is if the organization needed specific E3-only features, which is not part of the stated Copilot goal. Therefore, this is not a correct licensing solution.

Purchase a standalone Microsoft Defender for Office 365 Plan 2 subscription

Why wrong: 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 wrong: 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 wrong: 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.

Purchase Microsoft Purview Information Protection add-on

Why wrong: Purchasing Microsoft Purview Information Protection as an add-on is incorrect because this capability is already included in Microsoft 365 E5, making the purchase redundant. More importantly, Purview Information Protection (formerly Azure Information Protection) provides data classification, labeling, and encryption, but it does not control or change the geographic location where data is stored at rest. Data residency is a storage-location requirement, not a labeling or protection requirement, so this add-on would not satisfy the organization's residency needs.

Enable data residency by configuring Azure Information Protection policies

Why wrong: Configuring Azure Information Protection policies to 'enable data residency' is a misunderstanding: these policies define labels, retention rules, and encryption settings for documents and emails, but they have no effect on the physical datacenter or regional storage of Exchange Online mailboxes, SharePoint sites, or OneDrive accounts. Data residency requires a tenant-level placement feature, such as Microsoft 365 Multi-Geo, which is an add-on license. Without that licensing, any policy configuration merely controls access and classification—it does not move or pin data to a specific geographic region.

Purchase Microsoft Entra ID P2 licenses separately for all users

Why wrong: Purchasing Microsoft Entra ID P2 licenses separately for all users is both redundant and irrelevant in this scenario. Microsoft 365 E5 already includes Entra ID P2, so buying it separately would duplicate identity and access management coverage. Moreover, Entra ID P2 is an identity and security product—it provides features like Privileged Identity Management and Identity Protection, but it has no bearing on where data is stored at rest. Data residency is a workload placement issue, not an identity management issue, so this purchase would not fulfill the organization's residency requirement.