Derek Price

My feedback

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

    We’ll send you updates on this idea

    1 comment  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Derek Price commented  · 

    Is it documented somewhere that Azure MySQL ignores DEFAULT CURRENT_TIMESTAMP & ON UPDATE CURRENT_TIMESTAMP?

    Derek Price supported this idea  · 
  2. 191 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Storage » Queues  ·  Flag idea as inappropriate…  ·  Admin →
    Derek Price supported this idea  · 
  3. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Azure Functions » Bindings  ·  Flag idea as inappropriate…  ·  Admin →

    This feels a bit problematic – I’m not quite sure what is attempted here. It sounds like you want one queue per instance of the host, but hosts can be created and disposed at anytime so wary of allowing any dependencies on binding to an instance of the host. Feel free to add more context into the scenario and what is hope to be achieved.

    -
    Jeff

    An error occurred while saving the comment
    Derek Price commented  · 

    It's been nearly 6 months since I posted this, but I'll do my best to recall the issue:

    Several development environments and our staging environment share one storage container. To avoid collisions, I use a binding like this:

    {
    "type": "queueTrigger",
    "direction": "in",
    "name": "successTrigger",
    "queueName": "azure-webjobs-success-%AzureFunctionsWebHost:hostid%"
    },

    This works fine when I set the host ID explicitly, which I do for all the instances in our staging and production environments, but fails for the default hostid provided by the development environments.

    Incidentally, we do have a non-standard deployment. We are running our instances via the functions runtime docker container in our own AKS environment. The function runtime was already automatically giving each of our pods separate queues with names based on hostid for blob triggers, so I ended up having to supply a hostid explicitly in our production and staging environments to avoid having each one restart with its own, fresh, blob trigger queue.

    From there, it just seemed like a natural leap to use hostid in the names of our other triggers to avoid collision. In the dev environments, we only ever have one hostid, so it would make our lives a little easier to make it accessible when it isn't set explicitly, but the workaround is fairly simple - we just set it.

    Derek Price shared this idea  · 
  4. 162 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Storage » Queues  ·  Flag idea as inappropriate…  ·  Admin →
    Derek Price supported this idea  · 
  5. 1,976 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    91 comments  ·  Data Factory  ·  Flag idea as inappropriate…  ·  Admin →

    Great news – static IP range for Azure Integration Runtime is now available in all ADF regions! You can whitelist specific IP ranges for ADF as part of firewall rules. The IPs are documented here: https://docs.microsoft.com/en-us/azure/data-factory/azure-integration-runtime-ip-addresses#azure-integration-runtime-ip-addresses-specific-regions. Static IP ranges for gov cloud and China cloud will be published soon!

    Please refer to this blog post on how you can use various mechanisms including trusted Azure service and static IP to secure data access through ADF:
    https://techcommunity.microsoft.com/t5/azure-data-factory/azure-data-factory-now-supports-static-ip-address-ranges/ba-p/1117508

    Service tag support will be made available in next few weeks. Please stay tuned!

    If your network security requirement calls for ADF support for VNet and cannot be met using Trusted Azure service (released in Oct 2019), static IP range (released in Jan 2020), or service tag (upcoming), please vote for VNet feature here: https://feedback.azure.com/forums/270578-data-factory/suggestions/37105363-data-factory-should-be-able-to-use-vnet-without-re

    Derek Price supported this idea  · 
  6. 5,057 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    167 comments  ·  Storage » Blobs  ·  Flag idea as inappropriate…  ·  Admin →
    Derek Price supported this idea  · 
  7. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Azure Monitor- Alert Management  ·  Flag idea as inappropriate…  ·  Admin →
    Derek Price shared this idea  · 
  8. 6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Derek Price shared this idea  · 
  9. 34 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Kubernetes federation is not mature at this point. The v1 solution remains in an alpha state, with no path to GA. There is discussion around a V2 approach in sig-multicluster but it is still nascent. As a result, we have no near-term plans to enable it in AKS. If your goal is simply to run the same app across multiple clusters with traffic routing between them, you can mostly accomplish that with a good CI/CD pipeline and Azure Traffic Manager.

    Derek Price supported this idea  · 

Feedback and Knowledge Base