9 votesplanned · 1 comment · Azure Governance » Azure Resource Graph · Flag idea as inappropriate… · Admin →
8 votesunder review · 2 comments · Azure Active Directory » Application Proxy · Flag idea as inappropriate… · Admin →
Thanks for sharing your feedback. We will be further reviewing this feature as part of a set of feature improving logs available for App Proxy. We will update soon when we have more details.
10 votesunder review · 0 comments · Azure Active Directory » Application Proxy · Flag idea as inappropriate… · Admin →
13 votesunder review · 1 comment · Azure Active Directory » Application Proxy · Flag idea as inappropriate… · Admin →
We need more feedback around what are the key scenarios you want to accomplish with this integration. Please share with us more feedback on this as we continue investigating options for this,
IPv6 in Azure VNET is currently previewing globally- in ALL Azure Public cloud regions.
Announcement (Service Update): https://azure.microsoft.com/en-us/updates/public-preview-microsoft-adds-full-ipv6-support-for-azure-vnets/
Links to Documentation & Samples
Full documentation including sample scripts is available here: https://aka.ms/IPv6ForAzureVNETdoc
A sample JSON template is posted in the quickstart repository: https://azure.microsoft.com/en-us/resources/templates/ipv6-in-vnet/
Zone transfer is on our roadmap however not planned for CY 2019.
– Do you require zone transfers in to Azure DNS, or zone transfers out? Why?
To be able to build a hybrid DNS architecture on which 2 servers are onpremise (legacy) and some additional are out of onpremise legacy (Azure DNS). It will allow legacy DNS/Zone Management to stay onPremise/legacy process of the client and the infrastructure be more in the best practice (diversity (technology), diversity (datacenter/subnet/ASN/routing), diversity (root TLD of dns server)
– Do you require AXFR or IXFR?
– How should zone transfers be secured?
It have to be secured yes (whatever the way it is secured), the most important thing is the compatibility with other kind of DNS Services. The top 5 I have on our use case are
* Bind / https://www.isc.org/git/
* Knot / https://www.knot-dns.cz/
* NSD / https://www.nlnetlabs.nl/projects/nsd/about/
* PowerDNS / https://www.powerdns.com/
* and of course Microsoft DNS / https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc816603(v=ws.10)
A client wanted to use Azure as Virtual Datacenter and extend his Private Network by Express Route. Within this scenario the client already have its private DNS infrastructure with its own solution but not reluctant to Azure DNS if it was possible to integrate it (ie. zone delegation) like
Scenario 1 / client DNS (*.clientprivate) => Azure DNS (*.azure.clientprivate)
Scenario 2 / client DNS (*.clientprivate) => client DNS zone delgation (*.azure.clientprivate =>multiple Azure DNS delegation (*.spoke1.azure.clientprivate, *.spoke2.azure.clientprivate)
This is good feedback and is in our backlog but not currently under development. While we work on prioritizing/designing the feature, it’s helpful to hear from you how you would use this information in your scenarios. Please let us know by adding comments here.
Please add more comments to let us know what scenarios you’d complete using this feature, and upvote to help us understand its priority for you.
Marking this as part of our backlog. The votes and comments about how you would use this are really helpful, please keep voting/commenting if this is an interesting scenario for you.
Thanks for the feedback! I’m moving this to the Developer Experiences section as this seems like it’s broader than B2B (includes regular user create/update). Please keep adding scenarios and votes.
We do have some capabilities in this space by using either Access Reviews (https://docs.microsoft.com/en-us/azure/active-directory/governance/manage-guest-access-with-access-reviews) or the newly-released-to-preview Entitlement Management feature (https://docs.microsoft.com/en-us/azure/active-directory/governance/entitlement-management-overview).
If neither of those fulfill your requirements, please add a comment with your scenario for the feature to help us prioritize and design it better.
This feature is under review.
VNET peering will be greatly welcome, quite difficult to make some HUB/SPOKE architecture type without burning PIP/VIP within the backbone, just to make some peering and/or get a monolyth approach with a huge VNET subdivided in numerous subnet + UDR but everything within a big Subscription
Having SKU like "public cloud" like
* Basic (5 DTU / 2GB Storage)
* Standard (10 DTU S0, 20, 50, 100, 200, ...) and 250 GB Storage max
Could be usefull for deployment, ARM template and also Quota Definition on SQL Server.
Moreover it will open the ability to recharge/bill client/user based on SKU value reported within CDR (and not just base billing on number of SQL database instance and/or Storage consummed)