Eric JENOUVRIER

My feedback

  1. 7 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  2 comments  ·  Azure Active Directory » Application Proxy  ·  Flag idea as inappropriate…  ·  Admin →
    Eric JENOUVRIER supported this idea  · 
  2. 12 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure Active Directory » Application Proxy  ·  Flag idea as inappropriate…  ·  Admin →
    Eric JENOUVRIER supported this idea  · 
  3. 7 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Azure Active Directory » Application Proxy  ·  Flag idea as inappropriate…  ·  Admin →
    Eric JENOUVRIER supported this idea  · 
  4. 10 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  1 comment  ·  Azure Active Directory » Application Proxy  ·  Flag idea as inappropriate…  ·  Admin →
    Eric JENOUVRIER supported this idea  · 
  5. 52 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  Azure Active Directory » Application Proxy  ·  Flag idea as inappropriate…  ·  Admin →
    Eric JENOUVRIER supported this idea  · 
  6. 1,573 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    67 comments  ·  Networking » IPv6  ·  Flag idea as inappropriate…  ·  Admin →

    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/

    Eric JENOUVRIER supported this idea  · 
  7. 30 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Azure Stack » Network  ·  Flag idea as inappropriate…  ·  Admin →
    Eric JENOUVRIER shared this idea  · 
  8. 11 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Azure Active Directory » Conditional Access  ·  Flag idea as inappropriate…  ·  Admin →
    Eric JENOUVRIER supported this idea  · 
  9. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Azure Stack » Network  ·  Flag idea as inappropriate…  ·  Admin →
    Eric JENOUVRIER shared this idea  · 
  10. 927 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    48 comments  ·  Networking » DNS  ·  Flag idea as inappropriate…  ·  Admin →
    Eric JENOUVRIER supported this idea  · 
    Eric JENOUVRIER commented  · 

    – 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?

    AXFR

    – 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)

    Eric JENOUVRIER commented  · 

    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)

  11. 3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure Active Directory » B2B  ·  Flag idea as inappropriate…  ·  Admin →
    Eric JENOUVRIER supported this idea  · 
  12. 20 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Azure Active Directory » B2B  ·  Flag idea as inappropriate…  ·  Admin →
    Eric JENOUVRIER supported this idea  · 
  13. 25 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Azure Active Directory » B2B  ·  Flag idea as inappropriate…  ·  Admin →
    Eric JENOUVRIER supported this idea  · 
  14. 28 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Azure Active Directory » B2B  ·  Flag idea as inappropriate…  ·  Admin →
    Eric JENOUVRIER supported this idea  · 
  15. 61 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Azure Active Directory » Developer Experiences  ·  Flag idea as inappropriate…  ·  Admin →
    Eric JENOUVRIER supported this idea  · 
  16. 120 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    15 comments  ·  Azure Active Directory » B2B  ·  Flag idea as inappropriate…  ·  Admin →

    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.

    /Elisabeth

    Eric JENOUVRIER supported this idea  · 
  17. 353 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Azure Stack » Network  ·  Flag idea as inappropriate…  ·  Admin →
    Eric JENOUVRIER commented  · 

    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

    Eric JENOUVRIER supported this idea  · 
  18. 19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Azure Stack » PaaS  ·  Flag idea as inappropriate…  ·  Admin →
    Eric JENOUVRIER commented  · 

    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)

  19. 36 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Azure Stack » Portal  ·  Flag idea as inappropriate…  ·  Admin →
    Eric JENOUVRIER shared this idea  · 
  20. 21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Azure Stack » Network  ·  Flag idea as inappropriate…  ·  Admin →
    Eric JENOUVRIER supported this idea  · 
← Previous 1 3

Feedback and Knowledge Base