Work on this feature has started. Will update here when this becomes generally available.
Thank you for your suggestion and 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.
@Nasos, please reach out to me as well to setup a custom domain. Thanks in advance.
196 votesstarted · 15 comments · API Management » API management experience · Flag idea as inappropriate… · Admin →
The ability to rename databases and collections is not currently something that is in our road map.
Currently the way to accomplish this task in Cosmos DB is to create a new collection with the changed name then use bulk exec or change feed to populate it.
Thanks for your request and input on this. We may consider this for a future planning cycle.
How is this BASIC functionality not available 2+ years later from the original post?
DNSSEC remains on our long term roadmap, however it is unlikely to be available in CY 2019. If DNSSEC is a critical and immediate requirement for your business we’d suggest that you consider evaluating 3rd party DNS hosting solutions that provide this feature.
Work for this feature is now planned. Will update here when work on this feature starts and when it becomes generally available.
This is currently not on our roadmap. However, we will continue to review this item in the future as we prioritize future releases.
Thank you for your suggestion and for the comments.
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 work is on our backlog and currently under consideration. We will update here if this changes.
We understand this is a top customer ask and as such it is currently on our backlog to be prioritized. We will update when the status changes.
Waiting to exhale...
We have started work on the Vnet integration for Linux sites. The feature is currently in preview.
I will update this status as the engineering team progresses.
Excellent!!! Have been getting around it by putting storage and sql in a different region than the app service and using public ip filtering.
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?