Johan Ohlin
My feedback
-
1,827 votes
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.
https://docs.microsoft.com/en-us/azure/cosmos-db/local-emulator#running-on-mac-or-linuxWhen this feature is complete we will update here.
Thank you.
Johan Ohlin
supported this idea
·
-
259 votes
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 aadb2cpreview@microsoft.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?Johan Ohlin
supported this idea
·
-
214 votes
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
/Jose Rojas
Johan Ohlin
supported this idea
·
-
707 votes
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.
If you are looking to use custom domains to use javascript, we are now looking to enable that experience by providing a new (non-customizable) domain. Please look for updates here: https://feedback.azure.com/forums/169401-azure-active-directory/suggestions/15493536-add-support-for-javascript-inside-the-custom-ui-br
/Parakh
Johan Ohlin
supported this idea
·
-
967 votes
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.
Johan Ohlin
supported this idea
·
-
1,211 votes
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.
/Parakh
Old message:
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?Johan Ohlin
supported this idea
·
-
4,441 votes
Work on this feature has started. Will update here when this becomes generally available.
Thank you for your suggestion and votes.
Johan Ohlin
supported this idea
·
-
806 votes
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.
Johan Ohlin
supported this idea
·
-
896 votes
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.
Johan Ohlin
supported this idea
·
-
3,858 votes
Reopening this user voice item as our support for Skip/Take (Offset/Limit) was only limited to single partition queries.
Update.
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.
github.com/azure/azure-cosmos-dotnet-v3We 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.
Johan Ohlin
supported this idea
·
-
2,832 votes
Azure Cosmos DB now supports GROUP BY queries! With GROUP BY, you can run queries that group your results according to the values of one or more specified properties. This feature is currently supported in Data Explorer, JavaScript SDK 3.4, and .NET SDK 3.3. Support for other SDKs will be available later this year.
Johan Ohlin
shared this idea
·
-
277 votes
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.
Thanks,
Luis Cabrera
Azure Search Product TeamJohan Ohlin
supported this idea
·
-
383 votesJohan Ohlin
supported this idea
·
-
643 votes
Thank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Mike
Azure Search Product TeamJohan Ohlin
supported this idea
·
-
249 votes
Sorry, resolved the wrong entry. Shutdown not yet supported.
Johan Ohlin
supported this idea
·
-
99 votesJohan Ohlin
supported this idea
·
-
447 votes
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)
Johan Ohlin
supported this idea
·
-
1,312 votes
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.
Johan Ohlin
supported this idea
·
-
5,058 votes
Thanks for the feedback! We are interested in collecting feedback on this request – please vote for it if this is something you like to see.
We’re also interested in learning more what people want to use the SFTP/FTPS for and which protocol they prefer. Please feel free to leave us a comment letting us know more detail!
Thanks,
Will Gries
Program Manager, Azure FilesJohan Ohlin
supported this idea
·
-
1,081 votes
Thank you for your feedback. We view this ask as a set of related features.
Soft delete for blobs enables you to save and recover your data where blobs or blob snapshots are deleted. It does not protect against container or account deletion. This feature is currently generally available. You can see the announcement here: https://azure.microsoft.com/en-us/blog/soft-delete-for-azure-storage-blobs-ga/ and the full documentation here: https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-soft-delete
Object versioning will also offer object-level protection, and will offer a few incremental improvements to soft delete. Specifically, it will make recovery of deleted data easier. This feature is planned for the coming year.
Container soft delete will protect against container-level deletion and modification. This feature is planned for the coming year as well.
Native support for blob backup will protect against account-level deletion and modification, and is currently on our backlog.
We will provide updates when they become available. For any further questions, or to discuss your…
Johan Ohlin
supported this idea
·
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..