> For the complete documentation index, see [llms.txt](https://docs.novacura.com/extensibility-and-integration/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/extensibility-and-integration/products/active-directory/openid/upn-transformation.md).
# UPN Transformation
Flow Classic.
Issue: you have guest users in your Entra ID from different identity providers (for example, Gmail, O356, etc). Typically perhaps having different subcontractors or suppliers that you wish to log on to your Flow.
An issue could then be that you cannot find a common denominator between the IDPs'.
Perhaps 'email' works as a UserNameClaimsKey for supplier A, but not for supplier B since they use 'upn'.
A workaround worth considering could be to create a transformation rule in EntraID. In the example below internal users (non "EXT", meaning non guest users) get their user.mail value, and for externals users.userprincipalname is being used. This is just an example transformation.
The name you give your transformation is then what you map to the UserNameClaimsKey under the OpenID setting in Flow Studio
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.novacura.com/extensibility-and-integration/products/active-directory/openid/upn-transformation.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
