Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

Tom Hebert

My feedback

  1. 12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  (General Feedback) » Availability  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Tom Hebert commented  · 

    One problem. Azure UPv6 pricing seems to be focused on individual IP addresses. A /56 prefix would be pretty expensive. I understood pricing per IP address for IPv4. The resource is very limited. IPv6, not so much. Pricing would be better served by /56 prefix, for which my ISP charges us nothing.

    Tom Hebert supported this idea  · 
  2. 362 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    44 comments  ·  Azure Active Directory » Domain Join  ·  Flag idea as inappropriate…  ·  Admin →
    Tom Hebert supported this idea  · 
    An error occurred while saving the comment
    Tom Hebert commented  · 

    @BenTheBuilder is spot on. For large organizations, maintaining AD is fine. But for many others, it's overkill. Imagine the scenario where you are supporting a small business having two servers. In order to use AD, you need to maintain an AD server and best practice says two. AD domains are fragile and must be carefully operated or you will be finding yourself researching and fixing very complex issues.

    This hypothetical business really wants single sign on, two-factor authorization, and some basic things. Their one and only admin has full control anyway. Pushing complex group policies is just an unnecessary complication. Most other things associated with AD are an unnecessary costly distraction.

    Finally, a simplified on-premise environment is much easier to move to Azure. When I do this, the first thing I do is provision a replicate domain server in Azure, mainly to ensure that authentication can occur should the site-to-site VPN go down.

  3. 476 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    unplanned  ·  71 comments  ·  Azure Portal » Resource management  ·  Flag idea as inappropriate…  ·  Admin →
    Tom Hebert supported this idea  · 

Feedback and Knowledge Base