| Category | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| business-premium | M365bp Upgrade Windows Pro | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/business-premium/m365bp-upgrade-windows-pro.md | -localization_priority: Normal +ms.localizationpriority: medium search.appverid: - MET150 - MOE150 |
| enterprise | Manage Microsoft 365 Tenants With Windows Powershell For Delegated Access Permissio | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/manage-microsoft-365-tenants-with-windows-powershell-for-delegated-access-permissio.md | - Title: "Manage Microsoft 365 tenants with Windows PowerShell for DAP partners"--- Previously updated : 08/10/2020----- MET150--- scotvorg-- Ent_O365-- M365-subscription-management-- NOCSH- - - seo-marvel-apr2020 - - has-azure-ad-ps-ref -description: In this article, learn how to use PowerShell for Microsoft 365 to manage your customer tenancies. ---# Manage Microsoft 365 tenants with Windows PowerShell for Delegated Access Permissions (DAP) partners --*This article applies to both Microsoft 365 Enterprise and Office 365 Enterprise.* --Windows PowerShell allows Syndication and Cloud Solution Provider (CSP) partners to easily administer and report on customer tenancy settings that aren't available in the Microsoft 365 admin center. Administer on Behalf Of (AOBO) permissions are required for the partner administrator account to connect to its customer tenancies. --Delegated Access Permission (DAP) partners are Syndication and Cloud Solution Providers (CSP) Partners. They're frequently network or telecom providers to other companies. They bundle Microsoft 365 subscriptions into their service offerings to their customers. When they sell a Microsoft 365 subscription, they're automatically granted Administer On Behalf Of (AOBO) permissions to the customer tenancies so they can administer and report on the customer tenancies. -## What do you need to know before you begin? --The procedures in this topic require you to connect to [Connect to Microsoft 365 with PowerShell](connect-to-microsoft-365-powershell.md). ---You also need your partner tenant administrator credentials. --## What do you want to do? --### List all tenant IDs --> [!NOTE] -> If you have more than 500 tenants, scope the cmdlet syntax with either _-All_ or _-MaxResultsParameter_. This applies to other cmdlets that can give a large output, such as **Get-MsolUser**. --To list all customer tenant Ids that you have access to, run this command. --```powershell -Get-MsolPartnerContract -All | Select-Object TenantId -``` --This displays a listing of all your customer tenants by **TenantId**. -->[!Note] ->PowerShell Core does not support the Microsoft Azure Active Directory module for Windows PowerShell module and cmdlets with **Msol** in their name. To continue using these cmdlets, you must run them from Windows PowerShell. -> --### Get a tenant ID by using the domain name --To get the **TenantId** for a specific customer tenant by domain name, run this command. Replace _<domainname.onmicrosoft.com>_ with the actual domain name of the customer tenant that you want. --```powershell -Get-MsolPartnerContract -DomainName <domainname.onmicrosoft.com> | Select-Object TenantId -``` --### List all domains for a tenant --To get all domains for any one customer tenant, run this command. Replace _\<customer TenantId value>_ with the actual value. --```powershell -Get-MsolDomain -TenantId <customer TenantId value> -``` --If you have registered additional domains, this returns all domains associated with the customer **TenantId**. --### Get a mapping of all tenants and registered domains --The previous PowerShell for Microsoft 365 commands showed you how to retrieve either tenant IDs or domains but not both at the same time, and with no clear mapping between them all. This command generates a listing of all your customer tenant IDs and their domains. --```powershell -$Tenants = Get-MsolPartnerContract -All; $Tenants | foreach {$Domains = $_.TenantId; Get-MsolDomain -TenantId $Domains | fl @{Label="TenantId";Expression={$Domains}},name} -``` --### Get all users for a tenant --This displays the **UserPrincipalName**, the **DisplayName**, and the **isLicensed** status for all users for a particular tenant. Replace _\<customer TenantId value>_ with the actual value. --```powershell -Get-MsolUser -TenantID <customer TenantId value> -``` --### Get all details about a user --If you want to see all the properties of a particular user, run this command. Replace _\<customer TenantId value>_ and _\<user principal name value>_ with the actual values. --```powershell -Get-MsolUser -TenantId <customer TenantId value> -UserPrincipalName <user principal name value> -``` --### Add users, set options, and assign licenses --The bulk creation, configuration, and licensing of Microsoft 365 users is particularly efficient by using PowerShell for Microsoft 365. In this two-step process, you first create entries for all the users you want to add in a comma-separated value (CSV) file and then import that file by using PowerShell for Microsoft 365. --#### Create a CSV file --Create a CSV file by using this format: --`UserPrincipalName,FirstName,LastName,DisplayName,Password,TenantId,UsageLocation,LicenseAssignment` --where: --- **UsageLocation**: The value for this is the two-letter ISO country/region code of the user. The country/region codes can be looked up at the[ISO Online Browsing Platform](https://go.microsoft.com/fwlink/p/?LinkId=532703). For example, the code for the United States is US, and the code for Brazil is BR.--- **LicenseAssignment**: The value for this uses this format: `syndication-account:<PROVISIONING_ID>`. For example, if you're assigning customer tenant users O365_Business_Premium licenses, the **LicenseAssignment** value looks like this: **syndication-account:O365_Business_Premium**. You'll find the PROVISIONING_IDs in the Syndication Partner Portal that you have access to as a Syndication or CSP partner.--#### Import the CSV file and create the users --After you have your CSV file created, run this command to create user accounts with non-expiring passwords that the user must change at first sign-in and that assigns the license you specify. Be sure to substitute the correct CSV file name. --```powershell -Import-Csv .\FILENAME.CSV | foreach {New-MsolUser -UserPrincipalName $_.UserPrincipalName -DisplayName $_.DisplayName -FirstName $_.FirstName -LastName $_.LastName -Password $_.Password -UsageLocation $_.UsageLocation -LicenseAssignment $_.LicenseAssignment -ForceChangePassword:$true -PasswordNeverExpires:$true -TenantId $_.TenantId} -``` --## See also --[Help for partners](https://go.microsoft.com/fwlink/p/?LinkId=533477) |
| enterprise | Manage Microsoft 365 With Windows Powershell For Delegated Access Permissions Dap P | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/manage-microsoft-365-with-windows-powershell-for-delegated-access-permissions-dap-p.md | Delegated Access Permission (DAP) partners are Syndication and Cloud Solution Pr > Some administrative tasks can only be done in PowerShell. The following articles show how Syndication and CSP partners use PowerShell to administer their customer tenancies:- -- [Manage Microsoft 365 tenants with Windows PowerShell for Delegated Access Permissions (DAP) partners](manage-microsoft-365-tenants-with-windows-powershell-for-delegated-access-permissio.md) - [Add a domain to a client tenancy with Windows PowerShell for Delegated Access Permission (DAP) partners](add-a-domain-to-a-client-tenancy-with-windows-powershell-for-delegated-access-pe.md) |
| frontline | Flw Devices | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/flw-devices.md | In a shared devices deployment, you can use app protection policies to ensure th - [Manage shared devices for your frontline](flw-shared-devices.md) - [Frontline worker management](/entra/fundamentals/frontline-worker-management)+- [Frontline worker device management overview in Microsoft Intune](/mem/solutions/frontline-worker/frontline-worker-overview) |
| frontline | Flw Setup Microsoft 365 | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/flw-setup-microsoft-365.md | Last updated 04/04/2023 To set up Microsoft 365 for frontline workers, follow this overall process: -1. **[Identify your scenarios](#step-1-identify-your-scenarios)**: Which scenarios do you want to implement for your frontline workers? After you have determined which scenarios you want, use the table below to identify the required apps and services for each scenario that you want to implement. +1. **[Identify your scenarios](#step-1-identify-your-scenarios)**: Which scenarios do you want to implement for your frontline workers? After you determine which scenarios you want, use the following table to identify the required apps and services for each scenario that you want to implement. 1. **[Set up your environment and core Microsoft 365](#step-2-set-up-your-environment-and-core-microsoft-365)**: Follow the Setup Guides in the Microsoft 365 admin center to set up Microsoft 365. Keep reading to learn how to access these guides. 1. **[Provision users, configure groups, and assign licenses](#step-3-provision-users-configure-groups-and-assign-licenses)**: Learn how to provision users and create groups in Microsoft Entra ID, then assign frontline licenses to your users.-1. **[Configure device enrollment](#step-4-configure-device-enrollment)**: Set up shared and personal devices to work with Microsoft 365 and Microsoft Teams and to allow your frontline workers to communicate more securely within your organization. +1. **[Set up and configure devices](#step-4-set-up-and-configure-devices)**: Set up shared and personal devices to work with Microsoft 365 and Microsoft Teams and to allow your frontline workers to communicate more securely within your organization. 1. **[Set up any other services needed for your scenario](#step-5-set-up-other-services)**: Set up services including Exchange, Outlook, SharePoint, and Microsoft Viva. 1. **[Configure security](#step-6-configure-security)**: Learn how to create security policies to keep your organization secure. 1. **[Configure apps](#step-7-configure-apps-for-your-scenario)**: After everything is set up and configured in the admin center, you can follow the guidance for your scenarios to further configure the apps you need for each scenario. The following table lists the scenarios for your frontline workers. You can read | [Corporate communications](flw-corp-comms.md) | [Microsoft Teams](#set-up-microsoft-teams) <br>[SharePoint](#set-up-sites-with-sharepoint-in-microsoft-365) <br>[Viva Connections](#set-up-viva-connections) <br>[Viva Engage](#set-up-your-organizations-social-network-with-viva-engage) | | [Virtual Appointments](virtual-appointments.md) | [Microsoft Teams](#set-up-microsoft-teams) | | [Engage your employees and focus on employee wellbeing](flw-wellbeing-engagement.md)| [Microsoft Teams](#set-up-microsoft-teams) <br>[SharePoint](#set-up-sites-with-sharepoint-in-microsoft-365) <br>[Viva Connections](#set-up-viva-connections) <br>[Viva Engage](#set-up-your-organizations-social-network-with-viva-engage) |-| [Schedule your team with Shifts](shifts-for-teams-landing-page.md) | [Microsoft Teams](#set-up-microsoft-teams) | +| [Manage your team schedules with Shifts](shifts-for-teams-landing-page.md) | [Microsoft Teams](#set-up-microsoft-teams) | | [Onboard new employees](/sharepoint/onboard-employees)| [Microsoft Teams](#set-up-microsoft-teams) <br>[SharePoint](#set-up-sites-with-sharepoint-in-microsoft-365) <br>[Viva Connections](#set-up-viva-connections) <br>[Viva Learning](#set-up-viva-learning)| | [Ongoing training](flw-onboarding-training.md) | [Microsoft Teams](#set-up-microsoft-teams) <br>[Viva Learning](#set-up-viva-learning) | | [Simplify business processes](simplify-business-processes.md) | [Microsoft Teams](#set-up-microsoft-teams) <br>[Power Apps, Power Automate, and Power BI](#set-up-power-apps-power-automate-and-power-bi) | -Some services are only included with F3 licenses, such as email and the Power Platform. Check out [Understand frontline worker user types and licensing](flw-licensing-options.md) to determine the type of licenses you'll need for your users. +Some services are only included with F3 licenses, such as email and the Power Platform. Check out [Understand frontline worker user types and licensing](flw-licensing-options.md) to determine the type of licenses you need for your users. ## Step 2: Set up your environment and core Microsoft 365 Now that you have Microsoft 365 set up, you can start to add users, organize the ### Provision users -Now that you have Microsoft 365 set up, you can start to add users, organize them into groups, and assign licenses. Before you provision frontline users, you should create new administrator accounts or review and update your existing [administrator accounts in Microsoft Entra ID](/azure/active-directory/roles/permissions-reference). [Learn more about what Microsoft Entra admin roles you might need for Microsoft 365](/microsoft-365/admin/add-users/about-admin-roles). +Before you provision frontline users, you should create new administrator accounts or review and update your existing [administrator accounts in Microsoft Entra ID](/entra/identity/role-based-access-control/permissions-reference). [Learn more about what Microsoft Entra admin roles you might need for Microsoft 365](/microsoft-365/admin/add-users/about-admin-roles). In this step, you'll create user identities for your frontline workers in Microsoft Entra ID. You can import users in three ways: -- **Integrate Microsoft Entra ID with an existing Active Directory instance:** [Microsoft Entra Connect](/azure/active-directory/hybrid/how-to-connect-install-prerequisites) replicates Active Directory user accounts to Microsoft Entra ID, allowing a user to have a single identity capable of accessing both local and cloud-based resources.+- **Integrate Microsoft Entra ID with an existing Active Directory instance:** [Microsoft Entra Connect](/entra/identity/hybrid/connect/how-to-connect-install-prerequisites) replicates Active Directory user accounts to Microsoft Entra ID, allowing a user to have a single identity capable of accessing both local and cloud-based resources. - **Integrate Microsoft Entra ID with a third-party identity solution:** Microsoft Entra ID supports integration with some third-party providers through federation. - [Learn how to use Okta for Hybrid Microsoft AAD Join](https://www.okta.com/resources/whitepaper/using-okta-for-hybrid-microsoft-aad-join/).- - [Learn how to configure PingFederate with Microsoft Entra Connect](/azure/active-directory/hybrid/how-to-connect-install-custom#configuring-federation-with-pingfederate). -- **Import users from your organization's HR systems:** [Microsoft Entra user provisioning service](/azure/active-directory/app-provisioning/plan-auto-user-provisioning) automates the creation, maintenance, and removal of user identities based on rules set by your organization.+ - [Learn how to configure PingFederate with Microsoft Entra Connect](/entra/identity/hybrid/connect/how-to-connect-install-custom#configuring-federation-with-pingfederate). +- **Import users from your organization's HR systems:** [Microsoft Entra user provisioning service](/entra/identity/app-provisioning/plan-auto-user-provisioning) automates the creation, maintenance, and removal of user identities based on rules set by your organization. - **On-premises HR systems:** You can use [Microsoft Identity Manager](/microsoft-identity-manager/microsoft-identity-manager-2016) to provision users from your on-premises HR systems to Active Directory or directly to Microsoft Entra ID.- - **Cloud-based HR systems:** Learn how to connect [SAP SuccessFactors](/azure/active-directory/saas-apps/sap-successfactors-inbound-provisioning-tutorial) and [Workday](/azure/active-directory/saas-apps/workday-inbound-tutorial#planning-your-deployment) to Microsoft Entra ID. + - **Cloud-based HR systems:** Learn how to connect [SAP SuccessFactors](/entra/identity/saas-apps/sap-successfactors-inbound-provisioning-tutorial) and [Workday](/entra/identity/saas-apps/workday-inbound-tutorial#planning-your-deployment) to Microsoft Entra ID. Use this table to validate your HR-driven user provisioning. |Test scenario |Expected results | |--|--| |New employee is created in the cloud HR app |The user account is provisioned in Microsoft Entra ID and can access assigned cloud resources. <br> If Microsoft Entra Connect Sync is configured, the user account also gets created in Active Directory. <br> The user can sign into Active Directory domain apps and perform their desired actions.|-|User is terminated in the cloud HR app |The user account is disabled in Microsoft Entra ID, and, if applicable, Active Directory. <br>The user canΓÇÖt sign into cloud or on-premises applications and resources assigned to them. | +|User is terminated in the cloud HR app |The user account is disabled in Microsoft Entra ID, and, if applicable, Active Directory. <br>The user canΓÇÖt sign into cloud or on-premises apps and resources assigned to them. | |Supervisor is updated in the cloud HR app |User remains active with the new mapping. | |HR rehires an employee into a new role. |The results depend on how the cloud HR app is configured to generate employee IDs. <br>If the old employee ID is reused for a rehire, the connector enables the existing Active Directory account for the user. <br>If the rehire gets a new employee ID, the connector creates a new Active Directory account for the user. | |HR converts the employee to a contract worker or vice-versa |A new Active Directory account is created for the new persona and the old account is disabled on the effective date of the conversion. | Use this table to validate your HR-driven user provisioning. ### Configure Microsoft Entra groups -Configuring groups in Azure AD allows you to create and manage policies and license assignments at scale. +Configuring groups in Microsoft Entra allows you to create and manage policies and license assignments at scale. -- **Assign a unique attribute to frontline workers:** The ability to identify all frontline workers is useful when applying groups to the frontline workforce or for validating that integrations between Microsoft Entra ID and HR systems are functioning properly. Organizations frequently use the Job ID attribute for this purpose. Depending on your organization's structure, you may also need [custom security attributes](/azure/active-directory/fundamentals/custom-security-attributes-overview) or [directory extension attributes](/azure/active-directory/develop/active-directory-schema-extensions).+- **Assign a unique attribute to frontline workers:** The ability to identify all frontline workers is useful when applying groups to the frontline workforce or for validating that integrations between Microsoft Entra ID and HR systems are functioning properly. Organizations frequently use the Job ID attribute for this purpose. Depending on your organization's structure, you might also need [custom security attributes](/entra/fundamentals/custom-security-attributes-overview) or [directory extension attributes](/entra/identity-platform/schema-extensions). - **Create Microsoft Entra groups and assign frontline users:** With Microsoft Entra groups, you can grant access and permissions to a group of users instead of for each individual user. Groups are used to manage users that all need the same access and permissions to resources, such as potentially restricted apps and services. Instead of adding special permissions to individual users, you create a group that applies the special permissions to every member of that group. -The table below includes recommendations for applying groups in frontline implementations. For more information on group types, membership types, and assignment, see the [Microsoft Entra documentation for groups and membership](/azure/active-directory/fundamentals/concept-learn-about-groups?context=%2Fazure%2Factive-directory%2Fenterprise-users%2Fcontext%2Fugr-context) and [managing groups](/azure/active-directory/fundamentals/how-to-manage-groups). For more information on security group limits and other Microsoft Entra service limits, see [Microsoft Entra service limits and restrictions](/azure/active-directory/enterprise-users/directory-service-limits-restrictions). +The following table includes recommendations for applying groups in frontline implementations. For more information on group types, membership types, and assignment, see the [Microsoft Entra documentation for groups and membership](/entra/fundamentals/concept-learn-about-groups) and [managing groups](/entra/fundamentals/how-to-manage-groups). For more information on security group limits and other Microsoft Entra service limits, see [Microsoft Entra service limits and restrictions](/entra/identity/users/directory-service-limits-restrictions). |Use case |Group type | ||--| The table below includes recommendations for applying groups in frontline implem |Manage access for users without automatic assignment to groups. |Security groups or distribution list (no limit applies) | |Create an email alias to distribute groups messages to groups of users without automatic user management. |Distribution list or assigned Microsoft 365 group | |Create an email alias or team in Microsoft Teams and manage membership automatically. |Microsoft 365 groups, dynamic user |-|Use [My Staff](/azure/active-directory/roles/my-staff-configure) to delegate permissions to frontline managers to view employee profiles, change phone numbers, and reset passwords. |[Administrative Unit](/azure/active-directory/roles/administrative-units) | +|Use [My Staff](/entra/identity/role-based-access-control/my-staff-configure) to delegate permissions to frontline managers to view employee profiles, change phone numbers, and reset passwords. |[Administrative unit](/entra/identity/role-based-access-control/administrative-units) | [Learn more about the different types of groups you can create in the Microsoft 365 admin center](/microsoft-365/admin/create-groups/compare-groups). The table below includes recommendations for applying groups in frontline implem You can add licenses to individual users or to groups of users in Microsoft Entra ID. Group assignment is the most scalable way to assign licenses to your frontline workers. You can assign one or more product licenses to a group. -[Learn more about group-based licensing](/azure/active-directory/fundamentals/active-directory-licensing-whatis-azure-portal) and [assigning licenses to groups](/azure/active-directory/enterprise-users/licensing-groups-assign). +[Learn more about group-based licensing](/entra/fundamentals/concept-group-based-licensing) and [assigning licenses to groups](/entra/identity/users/licensing-groups-assign). -You may need to [unassign licenses](../admin/manage/assign-licenses-to-users.md) if you're changing some users from E to F licenses. [Learn more about how to switch specific users from E to F licenses](switch-from-enterprise-to-frontline.md#switch-users-to-a-microsoft-365-f-plan). +You might need to [unassign licenses](../admin/manage/assign-licenses-to-users.md) if you're changing some users from E to F licenses. [Learn more about how to switch specific users from E to F licenses](switch-from-enterprise-to-frontline.md#switch-users-to-a-microsoft-365-f-plan). -## Step 4: Configure device enrollment +## Step 4: Set up and configure devices -Registering devices in Microsoft Entra ID creates a unique identity that can be used to secure and manage devices. [Learn more about Microsoft Entra device identity](/azure/active-directory/devices/). +See the following guidance: -### Shared device enrollment with Intune --**Android:** Automatically enroll Android devices into shared device mode with [Microsoft Intune](/mem/intune/enrollment/android-kiosk-enroll). [Learn more about enrolling shared devices in Intune](https://techcommunity.microsoft.com/t5/intune-customer-success/enroll-android-enterprise-dedicated-devices-into-azure-ad-shared/ba-p/1820093). --**iOS:** Not currently available. --### BYOD device enrollment with Intune --Use Microsoft Intune to keep your frontline workers' devices secure and protected. Learn more about how to enroll different types of BYOD devices in Intune: --- [Windows](/mem/intune/enrollment/windows-enrollment-methods#user-self-enrollment-in-intune)-- [Android](/mem/intune/enrollment/android-work-profile-enroll)-- [iOS](/mem/intune/enrollment/ios-enroll#user-owned-iosipados-and-ipados-devices-byod)--### Configuring devices for shared device mode with third-party mobile device management --Zero-touch provisioning of shared device mode isnΓÇÖt currently supported by third-party mobile device management(MDM) solutions. However, you can [manually configure shared device mode](/azure/active-directory/develop/tutorial-v2-shared-device-mode#set-up-an-android-device-in-shared-mode) for Android and iOS devices managed in third-party MDM solutions. --> [!NOTE] -> While these steps register the device in Microsoft Entra ID, they don't connect Microsoft Entra ID to the MDM solution. Conditional access won't be available for these devices. --[Learn more about configuration with VMware Workspace ONE](https://docs.vmware.com/en/VMware-Workspace-ONE-Access/21.08/ws1_access_connector_install/GUID-271C47F6-856C-40F0-97AB-A8AD95025F9C.html) and [SOTI](https://www.soti.net/mc/help/v15.0/en/console/configurations/advancedconfigurations/shareddevice/shareddevice.html). --If you choose to manually configure devices in shared device mode, youΓÇÖll need to take more steps to re-enroll Android devices in shared device mode when third-party MDM support is available by uninstalling and reinstalling Authenticator from the device. --To set up shared and personal devices to work with Microsoft 365 and Microsoft Teams and to allow your frontline workers to communicate more securely within your organization, see [Overview of device management for frontline workers](flw-devices.md). +- [Overview of device management for frontline workers](flw-devices.md) +- [Manage shared devices for frontline workers](flw-shared-devices.md) ## Step 5: Set up other services Using dynamic group backed shared mailboxes based on attributes such as Location ### Set up Microsoft Teams -Follow the guidance in [Deploy Teams at scale for frontline workers](deploy-teams-at-scale.md). +Follow the guidance in [How to find the best frontline team solution for your organization](frontline-team-options.md). ### Set up employee experiences with Microsoft Viva You can use all of these apps within Microsoft Teams. For more information about ## Step 6: Configure security -After provisioning users, enrolling your devices, and configuring your applications, youΓÇÖre now ready to create policies to secure your organizationΓÇÖs infrastructure resources. +After provisioning users, setting up devices, and configuring your apps, youΓÇÖre now ready to create policies to secure your organizationΓÇÖs infrastructure resources. -- **Conditional access:** Plan a [Microsoft Entra Conditional Access deployment](/azure/active-directory/conditional-access/plan-conditional-access).+- **Conditional access:** Plan a [Microsoft Entra Conditional Access deployment](/entra/identity/conditional-access/plan-conditional-access). - **App protection policies:** [Learn about app management in Microsoft Intune](/mem/intune/apps/app-management).-- **Multi-factor authentication:** Require [multi-factor authentication for Intune device enrollment](/mem/intune/enrollment/multi-factor-authentication).+- **Multifactor authentication:** Require [multifactor authentication for Intune device enrollment](/mem/intune/enrollment/multi-factor-authentication). -Once youΓÇÖre done setting up security policies, itΓÇÖs important for you to use a test user (non-admin) account to verify the policies work as expected, and to ensure that the end-user experience is right for your frontline workforceΓÇÖs needs. Some capabilities like multi-factor authentication and app protection policies can add additional steps to device enrollment or sign-on flows, which may not be acceptable for some frontline scenarios. +Once youΓÇÖre done setting up security policies, itΓÇÖs important for you to use a test user (non-admin) account to verify the policies work as expected, and to ensure that the end-user experience is right for your frontline workforceΓÇÖs needs. Some capabilities like multifactor authentication and app protection policies can add additional steps to device enrollment or sign-in flows, which might not be acceptable for some frontline scenarios. ## Step 7: Configure apps for your scenario Follow these best practices to set up Microsoft Teams for your frontline workfor Use **team templates** in the Teams admin center or by using PowerShell. You can use prebuilt templates or [create your own](/microsoftteams/get-started-with-teams-templates-in-the-admin-console#create-your-own-team-templates). You can also apply template policies to control which templates are available to your users in Teams. Learn more about [how to get started with team templates in the Teams admin center](/microsoftteams/get-started-with-teams-templates-in-the-admin-console) and [how to set up and deploy teams](/microsoft-365/frontline/deploy-teams-at-scale?#set-up-and-deploy-your-teams). A prebuilt frontline template is accessible from the Teams admin center with the template ID "com.microsoft.teams.template.Frontline". -The table below shows Teams applications commonly utilized in frontline solutions. Shifts, Approvals, and Walkie Talkie are present in the Teams mobile client out of the box. You can control which applications are available to all users in the Teams admin center. +The following table lists Teams apps commonly used in frontline solutions. Shifts, Approvals, and Walkie Talkie are present in the Teams mobile client out of the box. You can control which apps are available to all users in the Teams admin center. **Scenarios and apps** The table below shows Teams applications commonly utilized in frontline solution | :- | :-: | :-: | :-: | :-: | :-: | :-: | :-: | | [Team communication and collaboration](flw-team-collaboration.md) | ✅ | | ✅ | ✅ | | ✅ | ✅ | | [Corporate communications](flw-corp-comms.md) | | | | | | | |-| [Virtual Appointments with Microsoft Teams](virtual-appointments.md) | | ✅ | | | ✅ | | | +| [Virtual Appointments with Teams](virtual-appointments.md) | | ✅ | | | ✅ | | | | Wellbeing & engagement | | | | ✅ | | | ✅ |-| [Schedule your team with Shifts](shifts-for-teams-landing-page.md) | | | ✅ | | ✅ | ✅ | ✅ | +| [Manage your team schedules with Shifts](shifts-for-teams-landing-page.md) | | | | | ✅ | | | | [Training: Onboard new employees](/sharepoint/onboard-employees) | | | ✅ | | | ✅ | ✅ | | Ongoing training | | | ✅ | | | ✅ | ✅ | | [Simplify business processes](simplify-business-processes.md) | ✅ | | ✅ | | | ✅ | ✅ | | Manage sites, stores, and projects | ✅ | | ✅ | | | ✅ | ✅ | -[Learn more about Microsoft Teams apps](/microsoftteams/deploy-apps-microsoft-teams-landing-page#core-apps). +[Learn more about Teams apps](/microsoftteams/deploy-apps-microsoft-teams-landing-page#core-apps). |
| solutions | Plan External Collaboration | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/solutions/plan-external-collaboration.md | -localization_priority: medium +ms.localizationpriority: medium f1.keywords: NOCSH recommendations: false description: Learn the difference between guest collaboration and shared channels in Teams and how to choose which one to use. |
| topics | Faq Topics | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/topics/faq-topics.md | -localization_priority: Normal +ms.localizationpriority: medium description: Read commonly asked questions and answers about using Topics. |
| topics | Sharepoint Taxonomy | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/topics/sharepoint-taxonomy.md | -localization_priority: medium +ms.localizationpriority: medium description: Learn about how to find topics in Topics by using SharePoint taxonomy. |
| topics | Topic Experiences Knowledge Managers | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/topics/topic-experiences-knowledge-managers.md | -localization_priority: Normal +ms.localizationpriority: medium description: Learn how knowledge managers build and manage a knowledge base with Topics. |
| topics | Topic Experiences Topic Contributors | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/topics/topic-experiences-topic-contributors.md | -localization_priority: Normal +ms.localizationpriority: medium description: Learn how to contribute to topics in Topics |
| topics | Topics Language Support | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/topics/topics-language-support.md | -localization_priority: Normal +ms.localizationpriority: medium description: Find the languages available in Topics. |