Skip to content

Commit 5ab8f79

Browse files
author
ducnguye
committed
Update format
1 parent 159e42f commit 5ab8f79

1 file changed

Lines changed: 20 additions & 2 deletions

File tree

microsoft-365/frontline/deploy-flexible-membership-teams-at-scale.md

Lines changed: 20 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -74,37 +74,53 @@ To complete the steps in this article, you must be a Global Administrator or a T
7474
7575
1. In the left navigation of the [Teams admin center](https://admin.teams.microsoft.com), choose Frontline deployment > Manage frontline teams.
7676
2. In the table, choose Set up.
77+
7778
:::image type="content" source="media/flw-teams-admin-center.png" alt-text="Manage frontline teams in Teams admin center":::
79+
7880
3. On the Overview page, review the setup and prerequisites information.
7981
4. On the Frontline workers page, select the Entra groups that include your frontline workers. You can choose up to 10 Entra groups. You can change these groups, as needed, after you submit your setup.
82+
8083
:::image type="content" source="media/dtas-add-frontline-groups.png" alt-text="Adding frontline groups to frontline teams settings":::
84+
8185
5. On the Location page, select a Microsoft Entra attribute or a custom user attribute that defines the location your frontline employees work in. You can only choose one location attribute. You can change the attribute, as needed, after you submit your setup. For example, if you would like to create a team for each city, enter the “City” attribute and we will group frontline workers in the same city into teams.
8286
All custom attributes are case sensitive and must start with an "extension_" prefix. Only custom attributes of the String data type are supported.
87+
8388
:::image type="content" source="media/dtas-appoint-attr-for-location.png" alt-text="Choosing the Microsoft Entra attribute to define location in a organization":::
89+
8490
6. On the Team settings page, define a naming pattern for your teams by choosing a prefix. The prefix is applied using the "prefix-location" format to all your teams.
91+
8592
:::image type="content" source="media/dtas-select-team-template-prefix.png" alt-text="Choosing the Microsoft Entra attribute to define location in a organization":::
93+
8694
7. Choose a team template. The team template you choose defines the channel structure for all your frontline teams. [Learn more](/microsoftteams/get-started-with-teams-templates-in-the-admin-console) about team templates.
8795
> [!NOTE]
8896
> Currently, only team templates that are set to the English (United States) locale are supported. Keep in mind that the locale doesn't affect translation of the template or data residency. The locale setting is used only to distinguish between templates that have the same name that are created in different languages.
8997
8. Select up to 10 Microsoft Entra groups that include at least one frontline worker from each location to be made team owner.
9098
Every location you want to deploy must have at least one frontline worker set as team owner. Team owners can add or remove membership from their frontline teams. For example, team owners can be your frontline managers, department heads, and/or leads.
9199
You can change these groups, as needed, after you submit your setup.
92100
9. Review your settings, and then choose **Submit**.
101+
93102
:::image type="content" source="media/dtas-review-summary.png" alt-text="Review selections and submit":::
103+
94104
> [!NOTE]
95105
> Setup can take several hours to run. Refresh the Manage frontline teams page to get the latest status.
96106
97107
## Deploy your frontline teams
98108
1. After setup is completed, go to the Manage frontline teams page, and then select the Deploy button.
109+
99110
:::image type="content" source="media/dtas-frontline-teams-deploy.png" alt-text="Manage frontline teams for teams deployment":::
111+
100112
2. On the Deploy frontline teams page, you can review your settings and view the list of locations that don't yet have a frontline team created.
101113
3. In the table, select the locations that you want to create teams for.
114+
102115
:::image type="content" source="media/dtas-frontline-teams-deploy.png" alt-text="Select locations for a deployment":::
116+
103117
4. Select Deploy. This process can take several hours depending on how many teams you're creating.
104118
After deployment is completed, you'll see the number of deployed frontline teams in the Frontline teams card. You can also download a CSV file with a list of those teams.
119+
105120
:::image type="content" source="media/dtas-manage-frontline-after-deploy.png" alt-text="Manage frontline teams after a teams deployment":::
121+
106122
If an error occurred during the deployment process, you can download the error CSV file on the Deployment health card. Use the information in it to help resolve the errors, and then rerun the deployment experience.
107-
5. You can repeat this process for any frontline locations that don't have a team.
123+
5. You can repeat this process for any frontline locations that don't have a team.
108124

109125
## Manage your frontline teams
110126
You can manage your teams when changes happen in your organization.
@@ -113,7 +129,9 @@ Create new teams for newly opened locations:
113129
1. In the left navigation of the [Teams admin center](https://admin.teams.microsoft.com), choose Frontline deployment > Manage frontline teams.
114130
2. In the table, choose Deploy.
115131
3. Select the Refresh location button, and then proceed when prompted by the dialog box. This process can take several hours depending on the number of new locations.
132+
116133
:::image type="content" source="media/dtas-refresh-frontline-teams.png" alt-text="Refesh locations in deploy frontline teams page":::
134+
117135
4. After the refresh is completed, your setup status shows as Complete. You can proceed to deploy your new teams. Deployment can take several hours depending on how many new teams you're deploying.
118136

119137
## Edit your frontline teams settings
@@ -129,6 +147,7 @@ Create new teams for newly opened locations:
129147
| Team settings - team name prefix | All existing team names will be updated to reflect the prefix and location name if it was changed. | All new teams will have the updated naming convention. |
130148
| Team settings - team template | No updates to the team structure will occur. | All new teams will have the updated naming convention. |
131149
| Identify your team owners | Frontline managers that were already assigned team owner won't be removed or reprieved of their team owner role. New team owners from the new groups you selected will be added as team owners to their respective teams. | All new teams will have team owners that are part of the new groups you selected. There must be at least one team owner for every new team. |
150+
132151
:::image type="content" source="media/dtas-edit-frontline-settings" alt-text="Edit frontline teams settings":::
133152

134153
## Get analytics on frontline teams usage
@@ -143,7 +162,6 @@ Seeing zero users next to a location name (ex. “Redmond”) in the deploy team
143162
### Why am I not seeing some locations?
144163
The locations displayed in the deploy teams table are the list of unique location values from the users in the selected owner groups. This is to ensure the team deploys successfully as owners are mandatory. This means that an admin can create a team with only owners and no members as well(please see “Why am I seeing 0 users while trying to deploy?” FAQ for more information on this scenario).
145164

146-
147165
## Related articles
148166
- [Learn where to start with a frontline deployment](flw-deploy-overview.md)
149167
- [How to find the best frontline team solution for your organization](frontline-team-options.md)

0 commit comments

Comments
 (0)