186 votes9 comments · Azure Kubernetes Service (AKS) » Integration with Azure services · Flag idea as inappropriate… · Admin →Anonymous commented
Furthermore, tags are not inherited to the new RG. We use tags for billing, so aks is now "free" as they don't have a cost center tag like the original RG. (We are now doing some nasty stuff, like capturing the creation from event grid and applying them that way. But it simply shouldn't be like that).
Why not doing like you do when provisioning Service Fabric Clusters? You'll get SFC and then the VM Scaleset right next to it. Simple and easy to maintain
Thank you for your feedback. We’re considering this for a future release of Azure Search.
Azure Search Product Team
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!
Program Manager, Azure Files
This ask is currently on our backlog and will be prioritized accordingly. We will update when the status changes.
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.
We’re pleased to announce a public preview of our Key Vault references feature, which you can learn more about here: https://azure.microsoft.com/en-us/blog/simplifying-security-for-serverless-and-web-apps-with-azure-functions-and-app-service/
There are some limitations to the initial preview, but we’re hoping to address those very soon. We’re looking forward to your feedback!
Matthew, Azure Functions team
We’ve put out a new version of the sign in policy called sign in v2. This is available through the new portal experience and we have rebranded policies as user flows. Please give this a try and give us feedback through this link: https://microsoft.qualtrics.com/jfe/form/SV_0Gu45RkBy2YR1kh
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 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
You can now use the Azure CDN to access blobs with custom domains over HTTPS. See the following article for instructions on how to do so: https://docs.microsoft.com/en-us/azure/storage/storage-https-custom-domain-cdn. Having talked to a number of customers, we concluded that this solution addresses many scenarios where the need for HTTPS access to blobs with custom domains exists.
Native Azure Storage support for using SSL to access blobs at custom domains is still on our backlog. We would love to hear about your scenarios where using the Azure CDN is not an acceptable solution, either by posting on this thread or sending us an email at email@example.com.
Thank you for the feedback. The product team has noted this suggestion and will consider it if resourcing allows.Anonymous shared this idea ·
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.
This work is on our backlog and currently under consideration. We will update here if this changes.