{"question":{"id":19768,"htmlId":"question19768","kind":"SingleChoice","specVersion":null,"questionHtml":"

An organization needs to provide additional Microsoft 365 features to specific users but wants to keep their current base license assignments unchanged. What is the most appropriate licensing strategy to achieve this?

","descriptionHtml":"

Assigning add-on licenses to the users allows the organization to add specific features or services without modifying their existing base licenses. This approach is cost-effective and targeted, providing only the necessary enhancements. Upgrading base licenses would change the user's primary license and could be more expensive if only certain features are needed. Purchasing separate, standalone licenses might not integrate correctly or be the intended method for adding features. Redistributing licenses does not introduce new capabilities and may cause compliance issues.

","answers":[{"id":2467137,"html":"

Upgrade the users' base licenses

","isCorrect":false},{"id":2467139,"html":"

Redistribute existing licenses among users

","isCorrect":false},{"id":2467138,"html":"

Purchase separate, standalone licenses for the features

","isCorrect":false},{"id":2467136,"html":"

Assign add-on licenses to the users

","isCorrect":true}],"textInput":null,"matching":null,"objectiveId":1754,"objectiveTitle":"Describe Microsoft 365 pricing, licensing, and support","nextQuestionUrl":"/study/questions/ms-900/an-organization-is-shifting-from-a-fully-on-premises-work-model-to-a-hybrid/19713?HideScore=false&ObjectiveMode=RoundRobbinObjectives","questionUrl":"/study/questions/ms-900/an-organization-needs-to-provide-additional-microsoft-365-features-to/19768","followUpPrompts":[{"id":347914,"prompt":"What are add-on licenses in Microsoft 365 and how do they differ from base licenses?","response":"Add-on licenses are optional SKUs you can assign to specific users to give them extra Microsoft 365 features without changing their existing base (primary) license. A base license (for example Microsoft 365 Business Standard or Office 365 E3) provides the core apps and services for a user. Add-ons layer additional capabilities—such as Audio Conferencing, Advanced Threat Protection (Microsoft Defender for Office 365), E5 Compliance add-ons, or Power Apps per‑app plans—on top of that base license. Key differences: - Scope: Base licenses define the primary product bundle for a user; add-ons provide targeted features. - Assignment: Add-ons are assigned in addition to a base SKU, not instead of it. A user needs the required base license (or compatible base SKU) before some add-ons can be applied. - Cost and flexibility: Add-ons let you pay only for extra capabilities for the users who need them, which is usually more cost‑effective than upgrading everyone’s base license. Note: SKU = stock‑keeping unit (identifier for a license type). Add-ons are the recommended approach when only a subset of users needs extra Microsoft 365 functionality."},{"id":347915,"prompt":"How do I assign add-on licenses to users in Microsoft 365?","response":"Quick steps (Admin center): 1. Sign in to the Microsoft 365 admin center as a global or billing/admin role. 2. Go to Users > Active users and select the user. 3. Choose Licenses and apps (or Edit product licenses). 4. Check the user’s base license (ensure compatibility), then check the add‑on SKU(s) you want to assign. 5. Save changes. For bulk operations or automation: use PowerShell or Microsoft Graph APIs. Typical approaches: - MSOnline or AzureAD modules (legacy) or the newer Microsoft Graph PowerShell module can add license SKUs programmatically. - Prepare a CSV list of users and target SKUs, then run a script to assign add-ons to each user. Best practices: verify add-on prerequisites (some add-ons require specific base SKUs), test on a small set of accounts first, track billing impacts, and document which users have which add-ons for compliance and cost control."},{"id":347916,"prompt":"When should I choose add-on licenses vs upgrading base licenses or buying standalone licenses?","response":"Use add-ons when only a limited set of users need extra capabilities and those capabilities are available as add-on SKUs—this keeps costs targeted and preserves existing base license assignments. Choose a base license upgrade when a large proportion of users need the higher feature set; upgrading at scale is often simpler and may be more cost‑efficient per user. Standalone licenses are appropriate when the product is outside the Microsoft 365 add-on ecosystem or when the feature is sold only as a separate product. Be cautious: standalone SKUs may not integrate as smoothly with existing M365 bundles and could complicate management or licensing compliance. Decision factors: - Number of users who need the feature (few = add-on; many = upgrade). - Availability of the feature as an add-on. - Long‑term roadmap (temporary vs permanent need). - Cost comparison (per‑user add-on cost vs upgrade cost). - Integration and management overhead. In short: prefer add-ons for targeted, temporary, or small‑group needs; upgrade base licenses for broad, ongoing needs; use standalone licenses only when no suitable add-on exists or product is separate."}],"presentationMode":false,"hideFeedbackForm":false,"hideResponseBadges":false,"setId":null,"skipSaveResponse":false},"canVote":false,"streak":{"value":null,"title":null,"launchConfetti":false,"isRecord":false},"id":"crucial-react-e7a9e28ccc00491197d945bab060739a"}

Microsoft 365 Fundamentals MS-900 Practice Question

Report Issue