Category | Microsoft Docs article | Related commit history on GitHub | Change details |
---|---|---|---|
commerce | Manage Multi Tenant Billing | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/commerce/billing-and-payments/manage-multi-tenant-billing.md | |
commerce | Allowselfservicepurchase Powershell | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/commerce/subscriptions/allowselfservicepurchase-powershell.md | Last updated 05/21/2024 # Use AllowSelfServicePurchase for the MSCommerce PowerShell module -The **MSCommerce** PowerShell module is now available on [PowerShell Gallery](https://aka.ms/allowselfservicepurchase-powershell-gallery). The module includes a **PolicyID** parameter value for **AllowSelfServicePurchase** that lets you control whether users in your organization can make self-service purchases of Microsoft or select third party offers. +The **MSCommerce** PowerShell module is available in the [PowerShell Gallery](https://aka.ms/allowselfservicepurchase-powershell-gallery). The module includes a **PolicyID** parameter value for **AllowSelfServicePurchase** that lets you control whether users in your organization can make self-service purchases of Microsoft or select third-party offers. ++You can also manage **AllowSelfServicePurchase** settings in the Microsoft 365 admin center. For more information, see [Manage self-service purchases and trials (for admins)](manage-self-service-purchases-admins.md). You can use the **MSCommerce** PowerShell module to: -- View the default state of the **AllowSelfServicePurchase** parameter valueΓÇöwhether it's enabled, disabled, or allows trials without a payment method+- View the default state of the **AllowSelfServicePurchase** parameter value—whether it's enabled, disabled, or allows trials without a payment method - View a list of applicable products and whether self-service purchase is enabled, disabled, or allows trials without a payment method - View or modify the current setting for a specific product to either enable or disable it - View or modify the setting for trials without payment methods To connect to the PowerShell module with your credentials, run the following com Connect-MSCommerce ``` -This command connects the current PowerShell session to a Microsoft Entra tenant. The command prompts you for a username and password for the tenant you want to connect to. If multi-factor authentication is enabled for your credentials, you use the interactive option to sign in. +This command connects the current PowerShell session to a Microsoft Entra tenant. The command prompts you for a username and password for the tenant you want to connect to. If multifactor authentication is enabled for your credentials, you use the interactive option to sign in. ## View details for AllowSelfServicePurchase The following table lists the available products and their **ProductId**. It als ## View a list of self-service purchase "third party offer types" and their status -To view a list of all available self-service purchase third party offer types and the status of each, run the following command: +To view a list of all available self-service purchase third-party offer types and the status of each, run the following command: ```powershell Get-MSCommerceProductPolicies -PolicyId AllowSelfServicePurchase -Scope OfferType Get-MSCommerceProductPolicies -PolicyId AllowSelfServicePurchase -Scope OfferTyp The following table lists the available third-party offer types. These offer types can be enabled or disabled for self-service purchase. -| Offer Type| Id | +| Offer Type| ID | |--|--| | Software as a Service | SaaS | | Power BI Visuals | POWERBIVISUALS | To allow users to try a specific product without a payment method, run the follo Update-MSCommerceProductPolicy -PolicyId AllowSelfServicePurchase -ProductId CFQ7TTC0KP0N -Value "OnlyTrialsWithoutPaymentMethod" ``` -To get the policy setting for a specific third party offer type, run the following command: +To get the policy setting for a specific third-party offer type, run the following command: ```powershell Get-MSCommerceProductPolicy -PolicyId AllowSelfServicePurchase -OfferType <ID> Get-MSCommerceProductPolicy -PolicyId AllowSelfServicePurchase -OfferType <ID> To enable the policy setting for a specific third-party offer type, run the following command: - ```powershell Update-MSCommerceProductPolicy -PolicyId AllowSelfServicePurchase -OfferType <ID> -Value "Enabled" ``` To disable the policy setting for a specific third-party offer type, run the following command: - ```powershell Update-MSCommerceProductPolicy -PolicyId AllowSelfServicePurchase -OfferType <ID> -Value "Disabled" ``` Update-MSCommerceProductPolicy -PolicyId AllowSelfServicePurchase -ProductId $pr If there are multiple values for the product, you can run the command individually for each value as shown in the following example: - ```powershell Update-MSCommerceProductPolicy -PolicyId AllowSelfServicePurchase -ProductId $product[0].ProductID -Value "Disabled" Update-MSCommerceProductPolicy -PolicyId AllowSelfServicePurchase -ProductId $product[1].ProductID -Value "Disabled" You see the following error message: > HandleError : Failed to retrieve policy with PolicyId 'AllowSelfServicePurchase', ErrorMessage - The underlying connection was closed: An unexpected error occurred on a send. -This may be due to an older version of Transport Layer Security (TLS). When you connect to this service, you must use TLS 1.2 or greater +This error might be due to an older version of Transport Layer Security (TLS). When you connect to this service, you must use TLS 1.2 or greater ### Solution |
commerce | Manage Self Service Purchases Admins | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/commerce/subscriptions/manage-self-service-purchases-admins.md | As an admin, you can't assign or unassign licenses for a purchase or trial subsc 4. The **Users** list is grouped by the names of people who made purchases or started trials. 5. To export a list of users with licenses for these subscriptions, select the subscriptions that you want to export, then select **Export users**. -## Enable or disable self-service purchases and trials +## Allow or block self-service purchases and trials -You can enable or disable self-service purchases and trials for users in your organization. The **MSCommerce** PowerShell module includes a **PolicyID** parameter value for **AllowSelfServicePurchase** that lets you control whether users in your organization can make purchases or start trials, and for which products. +You can allow or block self-service purchases and trials for users in your organization in two ways: -You can use the **MSCommerce** PowerShell module to do the following actions: +1. [By using the Microsoft 365 admin center](#use-the-microsoft-365-admin-center-to-allow-or-block-self-service-purchases-and-trials). +2. [By using the MSCommerce PowerShell module](#use-the-mscommerce-powershell-module-to-manage-self-service-purchases-and-trials). -- View the default state of the **AllowSelfServicePurchase** parameter valueΓÇöwhether it's enabled or disabled by product-- View a list of applicable products and whether purchases or trials are enabled or disabled for those products-- View or modify the current setting for a specific product to either enable or disable it+Both methods let you do the following tasks: ++- View a list of applicable products and their statuses. +- View or modify the current setting for a specific product. ++### Use the Microsoft 365 admin center to allow or block self-service purchases and trials ++> [!NOTE] +> You must be a Global Administrator to do the following steps. +++You can use the Microsoft 365 admin center to manage self-service purchases and trials for users in your organization. ++1. In the Microsoft 365 admin center, so to the **Settings** > <a href="https://go.microsoft.com/fwlink/p/?linkid=2053743" target="_blank">Org settings</a> page. +2. On the **Services** tab of the **Org settings** page, select **Self-service trials and purchases**. +3. The **Self-service trials and purchases** page lists the products that are eligible for self-service, and shows their current self-service setting. +4. To manage the settings for a specific product, select the product name. A panel opens and shows the current setting for the product you selected. +5. To change the setting for the product, select **Allow**, **Allow for trials only**, or **Do not allow**. +6. Select **Save changes**. ++### Use the MSCommerce PowerShell module to manage self-service purchases and trials ++The **MSCommerce** PowerShell module includes a **PolicyID** parameter value for **AllowSelfServicePurchase**. This parameter lets you control whether users in your organization can make purchases or start trials, and for which products. The module lets you do the same tasks available in the Microsoft 365 admin center, only from the command line. In addition, the module lets you view the default state of the **AllowSelfServicePurchase** parameter value for each product. > [!IMPORTANT] > When you use the **AllowSelfServicePurchase** policy, it controls both purchases and trials. For a list of the products available, see [View a list of self-service purchase products and their status](allowselfservicepurchase-powershell.md#view-a-list-of-self-service-purchase-products-and-their-status). You can assign existing licenses or buy extra subscriptions through existing agr 1. In the <a href="https://go.microsoft.com/fwlink/p/?linkid=2024339" target="_blank">admin center</a>, go to the **Billing** > <a href="https://go.microsoft.com/fwlink/p/?linkid=868433" target="_blank">Purchase services</a> page. For some customers, the page is named **Marketplace**. 2. Find and select the product that you want to buy, then select **Buy**.-3. Complete the remaining steps to complete your purchase. +3. To complete your purchase, complete the remaining steps. 4. To export a list of users to reference in the next step, follow the steps in [View who has licenses for a self-service purchase or trial subscription](#view-who-has-licenses-for-a-self-service-purchase-or-trial-subscription).-5. Assign licenses to everyone who has a license in the other subscription. For instructions on how to do this, see [Assign licenses to users](../../admin/manage/assign-licenses-to-users.md). +5. Assign licenses to everyone who has a license in the other subscription. For instructions, see [Assign licenses to users](../../admin/manage/assign-licenses-to-users.md). 6. Contact the person who bought the original subscription and ask them to [cancel it](manage-self-service-purchases-users.md#cancel-a-subscription). ## Take over a self-service purchase or trial subscription |
enterprise | Office 365 Network Mac Perf Overview | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/office-365-network-mac-perf-overview.md | The Microsoft 365 Admin Center now includes aggregated network connectivity metr > ![Network performance page.](../media/m365-mac-perf/m365-mac-perf-page-nav.png) > [!NOTE]-> Network connectivity in the Admin Center supports tenants in WW Commercial but not GCC Moderate, GCC High, DoD or China. +> Network connectivity in the Admin Center supports tenants in WW Commercial and China (Operated by 21Vianet, released on 2024-09-23), but not GCC Moderate, GCC High, or DoD. When you first navigate to the network performance page, you have to configure your locations in order to see the map of global network performance, a network assessment scoped to the entire tenant, percentage of your users working remotely vs onsite, and a list of current issues to take action on and/or to research further. From the overview pane, you can drill down to view specific network performance metrics and issues by location. For more information, see [Network performance overview in the Microsoft 365 Admin Center](#network-connectivity-overview-in-the-microsoft-365-admin-center). |
frontline | Deploy Shifts At Scale | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/deploy-shifts-at-scale.md | Title: Deploy Shifts to your frontline teams at scale -+ audience: admin |
frontline | Manage Shifts Permissions Frontline Managers | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/manage-shifts-permissions-frontline-managers.md | |
frontline | Shifts Connector Blue Yonder Admin Center Manage | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/shifts-connector-blue-yonder-admin-center-manage.md | Title: Use the Microsoft 365 admin center to manage your Shifts connection to Bl -+ audience: admin |
frontline | Shifts Connector Blue Yonder Known Issues | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/shifts-connector-blue-yonder-known-issues.md | Title: Teams Shifts connector for Blue Yonder known issues -+ audience: admin |
frontline | Shifts Connector Blue Yonder Powershell Setup | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/shifts-connector-blue-yonder-powershell-setup.md | Title: Use PowerShell to connect Shifts to Blue Yonder Workforce Management -+ audience: admin |
frontline | Shifts Connector Powershell Manage | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/shifts-connector-powershell-manage.md | Title: Use PowerShell to manage your Shifts connection to Blue Yonder Workforce -+ audience: admin |
frontline | Shifts Connector Ukg Admin Center Manage | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/shifts-connector-ukg-admin-center-manage.md | Title: Use the Microsoft 365 admin center to manage your Shifts connection to UK -+ audience: admin |
frontline | Shifts Connector Ukg Known Issues | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/shifts-connector-ukg-known-issues.md | Title: Team Shifts connector for UKG Pro Workforce Management known issues -+ audience: admin |
frontline | Shifts Connector Ukg Powershell Manage | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/shifts-connector-ukg-powershell-manage.md | Title: Use PowerShell to manage your Shifts connection to UKG Pro Workforce Mana -+ audience: admin |
frontline | Shifts Connector Ukg Powershell Setup | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/shifts-connector-ukg-powershell-setup.md | Title: Use PowerShell to connect Shifts to UKG Pro Workforce Management -+ audience: admin |
frontline | Shifts Connector Ukg Prerequisites | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/shifts-connector-ukg-prerequisites.md | Title: Prerequisites and requirements for the Teams Shifts connector for UKG Pro -+ audience: admin |
frontline | Shifts Connector Wizard Ukg | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/shifts-connector-wizard-ukg.md | Title: Use the Shifts connector wizard to connect Shifts to UKG Pro Workforce Ma -+ audience: admin |
frontline | Shifts Connector Wizard | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/shifts-connector-wizard.md | Title: Use the Shifts connector wizard to connect Shifts to Blue Yonder Workforc -+ audience: admin |
frontline | Shifts Connectors | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/shifts-connectors.md | |
frontline | Shifts For Teams Landing Page | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/shifts-for-teams-landing-page.md | |
frontline | Shifts Frontline Manager Worker Roles | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/shifts-frontline-manager-worker-roles.md | |
lighthouse | M365 Lighthouse Manage Inactive Users | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-manage-inactive-users.md | description: "For Managed Service Providers (MSPs) using Microsoft 365 Lighthous # Manage inactive users in Microsoft 365 Lighthouse -Microsoft 365 Lighthouse provides visibility into all the users across your managed tenants that have been inactive for over six months. Inactive accounts may present security risks and tie up unused licenses. From the **Inactive users** page, you can track and clean up inactive accounts. +Microsoft 365 Lighthouse provides visibility into all the users across your managed tenants that have been inactive for over six months. Inactive accounts may present security risks and tie up unused licenses. From the **Inactive users** tab on the **Account management** page, you can track and clean up inactive accounts. -Lighthouse uses sign-in activity to detect inactive users accounts. The **Inactive users** page shows up to 500 inactive accounts for each tenant. +Lighthouse uses sign-in activity to detect inactive user accounts. The **Inactive users** tab shows up to 500 inactive accounts for each tenant. ## Review inactive users -1. In the left navigation pane in <a href="https://go.microsoft.com/fwlink/p/?linkid=2168110" target="_blank">Lighthouse</a>, select **Users** > **Account management** > **Inactive users**. +1. In the left navigation pane in <a href="https://go.microsoft.com/fwlink/p/?linkid=2168110" target="_blank">Lighthouse</a>, select **Users** > **Account management**. -2. On the **Inactive Users** tab, set filters to the desired result. +2. On the **Account management** page, select the **Inactive users** tab, and then set the filters to show the desired result. 3. From the list of tenants, expand any tenant to see a list of inactive users within the tenant. 4. Select any user to open the user details pane and see more information about the account. -5. Once you've determined that a user account is no longer needed, you can delete or block the account. At the minimum, you should block the user account to reduce security risks. From the user details pane, select **Block sign-in** or **Delete user**. +5. Once you determine that a user account is no longer needed, you can delete or block the account. At a minimum, you should block the user account to reduce security risks. From the user details pane, select **Block sign-in** or **Delete user**. ## Block sign-in for multiple user accounts -1. In the left navigation pane in <a href="https://go.microsoft.com/fwlink/p/?linkid=2168110" target="_blank">Lighthouse</a>, select **Users** > **Account management** > **Inactive users**. +1. In the left navigation pane in <a href="https://go.microsoft.com/fwlink/p/?linkid=2168110" target="_blank">Lighthouse</a>, select **Users** > **Account management**. -2. On the **Inactive users** tab, expand any tenant in the list to see a list of inactive users within the tenant, select the users you want to block, and then select **Block sign-in**. +2. On the **Account management** page, select the **Inactive users** tab, and then expand any tenant in the list to see a list of inactive users within the tenant. -3. In the **Manage sign-in status** pane, select **Block users from signing in**. +3. Select the users you want to block, and then select **Block sign-in**. -4. Select **Save**. +4. In the **Manage sign-in status** pane, select **Block users from signing in**. ++5. Select **Save**. ## Related content |
lighthouse | M365 Lighthouse Manage Tenant List | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-manage-tenant-list.md | description: "For Managed Service Providers (MSPs) using Microsoft 365 Lighthous # Manage your tenant list in Microsoft 365 Lighthouse -To help you manage your tenant list in Microsoft 365 Lighthouse, you can apply custom tags to your tenants. These tags can be used to organize your tenants and can also help you filter the existing views and insights available to relevant sets of tenants. You can manage your tags from the Tenants page. Once tags are created and assigned, you can go to any page in Lighthouse that has a Tenants filter and use it to filter the data based on a tag. +To help you manage your tenant list in Microsoft 365 Lighthouse, you can apply custom tags to your tenants. These tags can be used to organize your tenants and can also help you filter the existing views and insights available to relevant sets of tenants. You can manage your tags from the **Tenants** page. Once tags are created and assigned, you can go to any page in Lighthouse that has a Tenants filter and use it to filter the data based on a tag. ## Before you begin You must be a Global Administrator in the partner tenant. Tags that are already assigned to the tenant have a check mark next to the tag name. -You can also assign a tag to multiple tenants by selecting the checkbox next to each tenant in the list that you want to tag, selecting **Assign Tags**, and then selecting a tag from the list. +To assign a tag to multiple tenants, select the checkbox next to each tenant in the list that you want to tag, select **Assign Tags**, and then select a tag from the list. > [!NOTE] > You can create up to 30 unique Tags and assign them to as many tenants as needed. You can also assign a tag to multiple tenants by selecting the checkbox next to 1. In the left navigation pane in <a href="https://go.microsoft.com/fwlink/p/?linkid=2168110" target="_blank">Lighthouse</a>, select **Tenants**. -2. From the list of tenants, select the three dots (more actions) next to the tenant that you want to edit, and then select **Tags**. +2. From the list of tenants, select the three dots (more actions) next to the tenant that has a tag you want to remove, and then select **Tags**. 4. Select the tag you want to remove. Tags that are currently assigned to the tenant have a check mark next to the name. -You can also remove a tag from multiple tenants by selecting the checkbox next to each tenant in the list that has a tag you want to remove, selecting **Assign Tags**, and then selecting a checked tag from the list. +To remove a tag from multiple tenants, select the checkbox next to each tenant in the list that has a tag you want to remove, select **Assign Tags**, and then select a checked tag from the list. ## Next steps -After you create and assign tags, you can use them to filter your tenants. Go to any page in Lighthouse that has a Tenants filter, select the filter, and then enter a tag to filter by or browse tags and select one or more tags from the list. You can also create new tags to support specific views based on each page. +After you create and assign tags, you can use those tags to filter your tenants. Go to any page in Lighthouse that has a Tenants filter, select the filter, and then enter a tag to filter by or browse tags and select one or more tags from the list. You can also create new tags to support specific views based on each page. ## Related content |
lighthouse | M365 Lighthouse Review Audit Logs | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-review-audit-logs.md | Microsoft 365 Lighthouse audit logs record actions that generate a change in Lig ## Before you begin -To view audit logs, you must have one of the following roles: +To view audit logs, you must hold one of the following roles: -- Microsoft Entra role: Global Administrator in partner tenant+- Microsoft Entra Global Administrator in your partner tenant -- Microsoft Partner Center role: Admin Agent+- Partner Center Admin agent > [!CAUTION] > To help keep your organization secure, Microsoft recommends that you use roles with the minimum level of permissions needed to perform a job. Global Administrator is a highly privileged role that should be limited to scenarios where you can't use a less-privileged role. To view audit logs, you must have one of the following roles: > [!NOTE] > It might take up to an hour to see new logs. Go to the respective service to see the most recent changes. -2. Select a tab to view specific logs: **Audit logs**, **Graph logs**, **Directory logs**, **Sign-in logs**. +2. Select one of the following tabs to view specific logs: **Audit logs**, **Graph logs**, **Directory logs**, **Sign-in logs**. 2. Filter the logs, as needed, by using the following options: - Audit logs tab |
lighthouse | M365 Lighthouse View Service Health | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/lighthouse/m365-lighthouse-view-service-health.md | description: "For Managed Service Providers (MSPs) using Microsoft 365 Lighthous You can view service health for the tenants you manage in Microsoft 365 Lighthouse. Service health includes incidents and advisories for several services, including Microsoft Intune, Microsoft Entra identity services, and mobile device management (MDM) cloud services. You can also see how many of your managed tenants are affected by incidents. For example, if one of your tenants is experiencing problems, you can check the Service health page to determine whether it's a known issue with a resolution in progress or whether a recent change might be impacting them. Checking service health could save you time troubleshooting and reduce support calls. -If you can't sign in to Lighthouse, you can use the [Microsoft 365 service health status page](https://status.office365.com/) to check for known issues preventing you from logging in to your partner tenant. Also, sign up to follow [@MSFT365status](https://twitter.com/MSFT365Status) on Twitter to see information on specific service incidents. +If you can't sign in to Lighthouse, you can use the [Microsoft Service Health Status](https://status.cloud.microsoft/) page to check for known issues preventing you from logging in to your partner tenant. Also, sign up to follow [@MSFT365status](https://twitter.com/MSFT365Status) on Twitter to see information on specific service incidents. ## Before you begin |
loop | Loop Workspaces Storage Permission | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/loop/loop-workspaces-storage-permission.md | Note: A feature for IT admins to assign additional temporary custodians during t ### In Loop components created in Microsoft 365 outside of the Loop app -Loop components created outside of Loop are stored in the OneDrive of the person who created the component. Therefore, if that user leaves the organization, the standard OneDrive IT policy is applied. +Loop components created outside of Loop are stored in the OneDrive of the person who created the component, or if created in a place with shared storage like a Teams channel, they are stored in the SharePoint folder for that channel. When stored in OneDrive, if that user leaves the organization, the standard OneDrive IT policy is applied. When stored in SharePoint, the standard SharePoint IT policy is applied. For more information on the storage location of components based on where they are created, see [Loop Storage](/microsoft-365/loop/loop-compliance-summary#loop-storage). |