94 votesunder review · 2 comments · Networking » Application Gateway · Flag idea as inappropriate… · Admin →
We are evaluating this feature ask. However, it is not on our immediate roadmap.
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.
Thank you for the feedback.
For internal networks, the Azure-provided DNS service already supports dynamic DNS update. However, this service does not enable you to specify your own DNS zone (that’s something we’re already tracking).
For the external networks, Azure DNS today only supports DNS updates via the Azure Resource Manager REST API (the Portal, PowerShell and CLI experiences sit on top of this API). We will consider whether dynamic DNS should also be supported, based on customer demand.
This is on our long term roadmap.
Thanks for posting the suggestion, we are tracking this on our backlog, however at the moment we don’t have an ETA.
Domain registration is being evaluated and remains on our long term road-map. However, it is not planned for CY 2019.
Just want to update
We’ve been doing some work for the in-portal views, including graphs and cost breakdown by resource. See docs https://docs.microsoft.com/azure/billing/billing-getting-started#usage
CSV improvements are coming, stay tuned.
All I want is the ability to rewind the burn rate graph and pie chart to the latest complete accounting period.
This is on our backlog and are reviewing this. Will revisit in an upcoming planning cycle.
Thank you for your suggestion.
This feature is now in preview for EF Core 2.2. To learn more, read the blog post and try here, https://blogs.msdn.microsoft.com/dotnet/2018/09/12/announcing-entity-framework-core-2-2-preview-2/
We plan to introduce support for tracking deletes in the change feed. Using this capability, you can integrate with Azure Functions or another event processing system to perform operations like execute procedure or call other services programmatically.
Quick update: We reduced the entry point to partitioned collections by 75% to make it more cost effective for applications that need high storage but low throughput.
Please see https://azure.microsoft.com/en-us/blog/azure-documentdb-entry-point-for-partitioned-collections-now-75-cheaper/ for details, and email us at firstname.lastname@example.org for any questions.
Oath support to our data plane is currently not on our road map. We will review this request in our next review cycle and will update here on its status.
Thank you for your suggestion and votes.
We want to provide get installations by tags, and I’d love to understand more about your scenarios around delete installations by tags and get/delete by push channel if you don’t mind sending me an email at email@example.com. Thanks!
Oh no. I teach a course on app building with a basic introduction to creating a backend in Azure. We currently teach the students to use Table Storage for simplicity. But now I see that Table Storage is useless for larger tables since skip isn't implemented! Please implement this ancient request for basic functionality, so that I don't set up my students for failure!
Thank you for your suggestion! This ask is currently on our backlog and will be prioritized accordingly. We will update this request when the status changes.
This work is on our backlog and currently under consideration. We will update here if this changes.
2 votes1 comment · Azure Monitor-Application Insights » Metrics & charting · Flag idea as inappropriate… · Admin →
Yup, in the 2.x SDK we now have SyntheticUserAgentTelemetryInitializer that by default is configured to mark requests with "AlwaysOn" as user-agent as synthetic.
2 votes0 comments · Azure Monitor-Application Insights » Metrics & charting · Flag idea as inappropriate… · Admin →