> For the complete documentation index, see [llms.txt](https://docs.intuneassistant.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intuneassistant.cloud/extensions/msp-support/license-management.md). # License Management Muti-Tenant Management (MSP) ## License Management How to add and remove licenses for customer tenants in your MSP environment ## [Tenant License Management](#tenant-license-management) Learn how to manage licenses for your customer tenants, including adding new licenses and removing existing ones through the customer settings interface. ### [Overview](#overview) License and module management is **MSP-only**: only MSP accounts can add or remove modules for the tenants they manage. Direct (non-MSP) accounts — whether on the free Community tier or a paid Enterprise plan — do not have any self-service license or module management. If a direct customer wants to change tier or add a module, they contact support; we update their account and add the modules they need. For MSPs, license management controls which features and capabilities are available for each customer tenant, through the Module Access section on that tenant's management page. Adding certain modules may separately require an admin consent process to grant the Graph API permissions that module needs. ### [Managing Tenant Licenses](#managing-tenant-licenses) #### [Accessing License Management](#accessing-license-management) {% stepper %} {% step %} Navigate to Customer Settings * Go to **Customer Settings** in your MSP account * View your list of managed customer tenants {% endstep %} {% step %} Access Tenant Actions * Find the customer tenant you want to manage * Click the **Actions** (pencil) icon in the tenant row * This opens the tenant's own management page {% endstep %} {% endstepper %} #### [Adding a Module](#adding-a-module) {% stepper %} {% step %} Click "Add" * In the Module Access section of the tenant's management page, find the module you want to enable * Click **Add** next to it — only modules your own customer license actually permits are shown; a module that isn't offered means your account needs to be upgraded first (contact support) {% endstep %} {% step %} Module Becomes Active * The module activates immediately for that tenant — no separate consent step for the activation itself * If the module requires additional Microsoft Graph permissions, those are requested the first time a feature that needs them is used, via the normal admin-consent flow {% endstep %} {% endstepper %} #### [Removing a Module](#removing-a-module) In the Module Access section of the tenant's management page, you can also remove an active module. {% stepper %} {% step %} Deactivate or Remove * Click the amber toggle icon next to an active module to deactivate it, or the trash icon to remove it permanently * Review the impact — the tenant immediately loses access to that module's features {% endstep %} {% endstepper %} Feature Impact Removing a module cannot be undone from the same screen — access to features provided by that module stops immediately. Re-adding it later starts a fresh activation. ### [Consent Management Process](#consent-management-process) #### [When Consent is Required](#when-consent-is-required) Consent is typically required when: * **Adding a new license** that requires additional permissions * **Upgrading license tiers** with expanded capabilities * **Enabling new features** that need extra Graph API access * **First-time setup** of advanced functionalities #### [Consent Workflow](#consent-workflow) {% stepper %} {% step %} Consent Request Triggered * System identifies required permissions for the new license * Consent dialog appears with permission details * Clear explanation of why permissions are needed {% endstep %} {% step %} Admin Consent Required * Global Administrator or appropriate admin role needed * Review of requested permissions and their impact * Decision to grant or deny the consent request {% endstep %} {% step %} Permission Activation * Once consent is granted, permissions are activated * License features become available immediately * User can access newly enabled capabilities {% endstep %} {% endstepper %} Consent Best Practice Review the permissions requested during consent carefully. Only grant permissions that are necessary for the intended license features. ### [License Status Indicators](#license-status-indicators) In the tenants list, license status is indicated with icons: * **No Consent needed**: - Indicates no license is assigned * **Consent needed**: - Indicates consent is required for the license #### [Consent license](#consent-license) If a license requires consent, you will see the red alert icon as show above. To provide consent go to the tenant using the action button and use the Grant Consent button. ### [Troubleshooting](#troubleshooting) #### [Module Addition Fails](#module-addition-fails) Possible causes: * Your MSP account's own customer license doesn't permit that module yet * You tried this from a Direct (non-MSP) account — module management is MSP-only Solutions: * Contact support to verify or upgrade your license #### [Consent Process Fails](#consent-process-fails) Possible causes: * Admin consent not properly granted * Permission conflicts with existing setup * Tenant policy restrictions, its not possible to grant the permissions Solutions: * Ensure Global Administrator grants consent * Review existing permissions for conflicts * Check tenant conditional access policies #### [Features Not Available After Module Addition](#features-not-available-after-module-addition) Possible causes: * Consent not completed successfully * Permission synchronization delay * License activation pending Solutions: * Complete the consent process if pending * Wait for permission synchronization (up to 30 minutes) * Contact support if issues persist ### [Related Documentation](#related-documentation) * [Permission Overview](/security-and-compliance/needed-permissions.md) * [MSP Permission Overview](/extensions/msp-support/multi-tenant-permissions.md) * [Switch Tenants](/extensions/msp-support/switch-tenants.md) * [Multi-Tenant Overview](/extensions/msp-support/overview.md) License Flexibility License management provides flexibility to scale features based on customer needs while maintaining security through proper permission management. [Multi-Tenant Permissions](/extensions/msp-support/multi-tenant-permissions.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.intuneassistant.cloud/extensions/msp-support/license-management.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.