Add automatic team provisioning instructions

[urseberry]

What does this PR do? What is the motivation?

Merge instructions

Merge readiness:

• Ready for merge

Merge queue is enabled in this repo. To have it automatically merged after it receives the required reviews, create the PR (from a branch that follows the <yourname>/description naming convention) and then add the following PR comment:

/merge

Additional notes

[github-actions]

Preview links (active after the build_preview check completes)

Modified Files

• https://docs-staging.datadoghq.com/uchen/managed-teams/account_management/scim/
• https://docs-staging.datadoghq.com/uchen/managed-teams/account_management/scim/okta
• https://docs-staging.datadoghq.com/uchen/managed-teams/account_management/teams/manage

[heavi5ide]

Thanks Ursula! Let me know when you want me to take another look :)

[heavi5ide]

Suggested change

	To verify that the operation completed successfully, navigate to the [Teams list][7]. Search for a Datadog team matching the Okta group you configured. Verify that the team exists in Datadog and is managed externally.
	To verify that the operation completed successfully, navigate to the [Teams list][7]. Search for a Datadog team matching the Okta group you configured. Verify that the team exists in Datadog and is managed externally. Note that it may take a minute or two for the team to show up in Datadog.

[heavi5ide]

Okta asked us to call out in our documentation that this option will not actually delete the team within Datadog. This is a potential point of confusion because the user is told to select "Delete the group in the target app" but within Datadog what we actually do is just remove the managed relationship and remove all members of the Team. This is because the Team in Datadog may be associated with other data and assets within Datadog, so we are conservative and do not actually delete it, to avoid doing something destructive to the data/configuration of the org's Datadog setup (for instance, breaking notifications that were using the Team as a routing destination that is forwarding notifications to a Slack channel).

I'm not sure of the best way to call this out here; in a way, the docs here are already clear on that, because you say above that

This procedure enables you to manage team membership in Datadog instead of Okta and removes the team members from the Datadog Team.

I think maybe just an extra clarification on this line could be helpful. Something like:

Suggested change

	1. Select **Delete the group in the target app (recommended)**.
	1. Select **Delete the group in the target app (recommended)**. (Note that despite the naming of this option in Okta, this will _not_ delete the team in Datadog)

Maybe there's a better/more clear option that you can think of 🤷

[heavi5ide]

Maybe a better suggestion: follow the same format as the "no match found" note from line 92, and put a separate note after the list of numbered steps like:

Note: Okta labels this option "Delete the group in the target app" but this will not actually delete the team in Datadog. All members will be removed from the team and it will no longer show as managed.

[heavi5ide]

Thanks Ursula!

[heavi5ide]

Suggested change

	**Note:** Okta may display a **No match found** message, because it only returns managed groups. You can ignore this message and proceed with creating the group to establish synchronization.
	**Note:** Okta will display a **No match found** message. You can ignore this message and proceed with creating the group to establish synchronization.

[heavi5ide]

Maybe a better suggestion: follow the same format as the "no match found" note from line 92, and put a separate note after the list of numbered steps like:

Note: Okta labels this option "Delete the group in the target app" but this will not actually delete the team in Datadog. All members will be removed from the team and it will no longer show as managed.