Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update teams-adoption-define-outcomes.md #8876

Open
wants to merge 1 commit into
base: public
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Teams/teams-adoption-define-outcomes.md
Original file line number Diff line number Diff line change
Expand Up @@ -122,7 +122,7 @@ Once you've selected your enablement strategy you'll be ready to revisit and sca

Example team level provisioning and management best practices:

|Team level | Who creates? | Lavels and retention | Considerations |
|Team level | Who creates? | Labels and retention | Considerations |
| --------- | ------------ | -------------------- | -------------- |
| Level 1 - Divisional | IT or champion for that group to name it properly | Confidential with standard retention policy applied and 1 year renewal policy | Think of this like reserving a domain name. You want control of how division teams are named and what's included. Design the team before adding additional users.|
| Level 2 - Project/service | Project owner or champion | Confidential or highly confidential depending on content. May have a retention policy. 6 month renewal. | Before creating this, think just beyond the boundary of the project or service you are working on. Would it make more sense to combine forces with another team? Make every effort to minimize the number of teams individual users have to visit when working on the same project or service.|
Expand Down