Why Multiple Identities?

# Issue Transfer

This issue has been transferred from the Azure SDK for .NET, [#24204](https://github.com/Azure/azure-sdk-for-net/issues/24204).

### Please be aware that @rjarrattmsft is the author of the original issue and include them for any questions or replies.

## Details

Under what circumstances could there be more than one identity?

---
#### Document Details

⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*

* ID: ee033456-b610-5325-5e48-ecb12b821c9b
* Version Independent ID: 99068dbe-d073-7199-e957-ece9c70b8db9
* Content: [HttpRequestData.Identities Property (Microsoft.Azure.Functions.Worker.Http) - Azure for .NET Developers](https://docs.microsoft.com/en-us/dotnet/api/microsoft.azure.functions.worker.http.httprequestdata.identities?view=azure-dotnet)
* Content Source: [xml/Microsoft.Azure.Functions.Worker.Http/HttpRequestData.xml](https://github.com/Azure/azure-docs-sdk-dotnet/blob/master/xml/Microsoft.Azure.Functions.Worker.Http/HttpRequestData.xml)
* GitHub Login: @rloutlaw
* Microsoft Alias: **routlaw**

Start with the HttpRequestData.Identities property documentation and its source in xml/Microsoft.Azure.Functions.Worker.Http/HttpRequestData.xml. Investigate the circumstances that produce more than one identity, then update the property documentation so that behavior is explained clearly. Done means the docs answer the reporter’s question without changing the linked API reference scope.

Written by the indexing model from the issue text.