We have started the planning for this feature and hope to have a preview by the end of the calendar year. In the meantime, could you respond to email@example.com with the answers to the following questions:
- In which scenarios do you plan to force the user to change his/her password?
- What kind of information (if any) would you like to get back if the user goes through the reset flow?
- Do you currently or plan to track which users have reset their password?
It would be nice to have some sort of response from the Azure AD team. Dint think Microsoft would leave its customers hanging high and dry after posting a message more than a year ago. Appalling!
We are working to support SP-initiated SSO as well. However, we don’t have timing on when it would available to customers.
The IDP initiated SSO custom policy links seems to be broken. Could you provide a working link please?
We continue evaluating several alternatives to provide full email customization. We are actively working on an alternative.
Unfortunately we do no yet have an ETA.
Thanks for the feedback! I’m moving this to the Developer Experiences section as this seems like it’s broader than B2B (includes regular user create/update). Please keep adding scenarios and votes.
We plan to start work on this in the next 6 months. Please note we don’t have timing on when it would be available for customers.
Due to various technical limitations, the first iteration of the customer-owned domains functionality will not be available for a few more months. We will provide an update as soon as we can get a more specific ETA.
Any updates on eta or how to apply for this?
10 votesDipesh A shared this idea ·