Hi @Bui Nguyen Viet Quy (FDN.FIN5) ,
Thanks for your post!
If you specify the inviteRedirectUrl
in the request body you will be able to customize where you want your users to land after redemption, but you cannot change the navigation of the inviteRedeemUrl.
https://learn.microsoft.com/en-us/graph/api/invitation-post?view=graph-rest-1.0&tabs=http
Note that Google has deprecated embedded web-view sign-in support so if your apps apps authenticate users with an embedded web-view and you're using Google federation, Google users won't be able to authenticate. The redemption flow for Gmail users requires them to enter a code in a separate browser window to finish signing in on Microsoft Teams mobile and desktop clients. This applies to invited guests and guests who signed up using Self-Service Sign-Up. https://learn.microsoft.com/en-us/azure/active-directory/external-identities/google-federation
If an admin has enabled Google federation, Azure AD checks if the user’s domain suffix is gmail.com, or googlemail.com and redirects the user to Google.
https://learn.microsoft.com/en-us/azure/active-directory/external-identities/redemption-experience
Let me know if this explanation helps and if you have further questions. The redemption flow for Google users does have some additional variables to consider.
If the information helped you, please Accept the answer. This will help us as well as others in the community who may be researching similar questions.