8 votesAnonymous shared this idea ·
This is a scenario we are looking to support in the future however, it is not on our immediate roadmap for the next 6 months. Please continue voting and we will evaluate at a later date.
We are looking to add additional MFA options for Azure AD B2C in the next few months. As part of the investigation, we want to learn more about your requirements. Email your feedback to email@example.com.
When you say “support for Microsoft Authenticator”, which feature are you referring to?
1. The ability to see the codes in the authenticator app
2. The ability to receive push notifications for MFA
If both, which do you prefer more?
Again, please email your feedback to firstname.lastname@example.org. Feel free to include more details about your scenarios/requirements!
We are still working on this one. We’re always passing your feedback along, but make sure you reach out to AAD as well so they hear your voice directly!
Sorry for the confusion around Microsoft Graph AAD integration. It won’t allow you to connect AAD events to Event Grid just yet, but you can get some AAD related events directly from Graph to work with: https://docs.microsoft.com/en-us/graph/overview-major-services#users-and-groups
We have reviewed this and have elected to not include this on our road map for the time being. We may revisit this in the future so will leave as unplanned rather than declined or closed.
Thanks for your suggestion and comments.
Thank you for your feedback. We’re considering this for a future release of Azure Search.
Azure Search Product Team
Azure Cosmos DB is a multi-model database service, and therefore supports accessing the same underlying data using any/all APIs. We are however implementing some platform-level changes to make data access from different APIs seamless like supporting conversions between disparate type systems, and capabilities.Anonymous commented
We're currently using several cosmos dbs via the graph api. We also use the document sdk to add more complex documents and then use gremlin to add edges between them and query those documents. The 'defaultExperience' setting on this db is set to 'graph' and because of this we can toy around in the portal and test queries, so far so good, but when I try to add a azure search indexer it fails because it's not a sql api experience. Could you therefore enable multi api support also UI wise, not just from an API point of view?
We are currently reviewing this for future inclusion on our roadmap. Will update here on status as this progresses.
Thank you for your suggestion
Apologies for the confusion on our part.
This is currently not on our roadmap. However, we will review this item in the future as we prioritize future releases.
Thanks for your suggestion.