Just a quick update. Work on this feature continues but is taking longer than expected.
We have recently published guidance how how users who can run Windows in a VM whether on Parallels or Virtual Box with a Mac or Linux host can use the Cosmos emulator. Please feel free to use this as a workaround.
When this feature is complete we will update here.
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 firstname.lastname@example.org 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?
Thank you. We will examine the experience of duplicate sign ups across Identity providers. Would performing this check by using the email address be sufficient?
BTW, Linking multiple provider accounts to one user is in our roadmap and we’ve already achieved it in preview…
We look forward to your feedback
We have released the public preview for this feature! Learn more about how to use it here: https://docs.microsoft.com/azure/active-directory-b2c/active-directory-b2c-setup-oidc-azure-active-directory
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.
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.
We definitely recognize the popularity of this feature, and we discuss it constantly during the planning phases. However there are certain technical limitations in the system that add a large amount of development cost. Because of the cost and the fact that there is a workaround available, other features get prioritized over this one.
That being said, please keep voting for it. The popularity of the feature does help bring it up and makes us reconsider every time.
Apologies for the delay.
We’re doing some research both on the specifics of this ask as well as what it would take to support this.
Is the ask here to do the same thing that regular Azure AD does (see: https://blogs.technet.microsoft.com/enterprisemobility/2014/12/18/azure-active-directory-now-with-group-claims-and-application-roles/) or is are there different requirements around this for Azure AD B2C?
Work on this feature has started. Will update here when this becomes generally available.
Thank you for your suggestion and votes.Johan Ohlin commented
The way I've understood it is that when you make an update, the whole object is replaced with the new object. From a data point of view this gives the same result as a real PATCH, but from an indexing point of view this gives a lot of overhead since the whole old object has to be removed from the index and the whole new object has to be added, even though you've only changed the value of one single property. If you have a large object, this can be an expensive operation. This is why Microsoft suggests that we use lots of small objects instead of big complex ones. So, being able to do real partial updates is still something we need..
Azure Cosmos DB supports the CONTAINS, STARTSWITH, and ENDSWITH built-in functions which are equivalent to LIKE.
We are planning to add support for LIKE since this is a top requested item, but meanwhile, please use the other equivalent keywords.
There are multiple responses to this suggestion.
Support for SQL-like syntax for UPDATE, DELETE and INSERT INTO are not on our road map at this time.
However, the underlying functionality for an UPDATE, SET is essentially a PATCH. This functionality we are actively working on. See this User Voice item here to track for future updates. https://feedback.azure.com/forums/263030-azure-cosmos-db/suggestions/6693091-be-able-to-do-partial-updates-on-document
Thank you for your suggestion.
Reopening this user voice item as our support for Skip/Take (Offset/Limit) was only limited to single partition queries.
The newly released .NET SDK v3 now includes support for x-partition queries using Offset/Limit. You can learn more about v3 SDK and try it and provide feedback on our github repo here.
We will also be back-porting this functionality to our .NET v2 SDK. This work will begin shortly and we anticipate it to be released in September.
Once that is released we will mark this feature as complete.
Thank you for your patience and votes.
This feature is currently in active development. We will update this item to complete once it has shipped so those voting/commenting will be notified.
Thank you for your patience.Johan Ohlin shared this idea ·
Thank you for your feedback. While it is unlikely we’ll address this suggestion in the next 6 months, we’ll reassess based on the number of votes it receives in the next 6 month cycle.
Azure Search Product Team
Thank you for your feedback. We’re considering this for a future release of Azure Search.
Azure Search Product Team
Sorry, resolved the wrong entry. Shutdown not yet supported.
this feature has been postponed as it wouldn’t be complete and might be revisited later if standards/supported features by CAs and browsers change (double wildcard certificates are not supported standard, resulting in no way to secure double wildcard domain)
We are looking at options to enable this.
Thank you for your feedback. We are currently in public preview of blob storage lifecycle management. The feature set offers a rich, rule-based policy engine which you can use to transition your data to the best access tier and to expire data at the end of its lifecycle. See our post on the Azure Blog to get started: https://azure.microsoft.com/en-us/blog/azure-blob-storage-lifecycle-management-public-preview/preview/.
For any further questions, or to discuss your specific scenario, send us an email at DLMFeedback@microsoft.com.