Clarify deduplication #154
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The section where we talk about deduplication (" as long as they are assigned to a default tenant, even across user providers.") is confusing to customers. A User Provider can only have 1 default tenant. Therefore, users will only be deduplicated if they belong to different User Providers (same as default tenants). With the current writing, it seems that different User Providers is an optional situation.
From different Support cases, we can see that customers believe that this sentence actually means that users in different tenants will be counted as 1 user only (inside the same or different User Providers), as long as one of the users belongs to the Default tenant. This is not true. We only discard users as duplicates if they exist across different default tenants (which, by definition, means different user providers).