Imre Pühvel

My feedback

  1. 77 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Azure Cosmos DB » Portal  ·  Flag idea as inappropriate…  ·  Admin →
    Imre Pühvel supported this idea  · 
  2. 59 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Imre Pühvel supported this idea  · 
  3. 1,371 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    155 comments  ·  Azure Active Directory » SaaS Applications  ·  Flag idea as inappropriate…  ·  Admin →

    We’re continuing to investigate options for adding this support. There are technical challenges to overcome in order to make this happen. We thank you for all your valuable comments so far, and welcome any additional feedback you have on what are the most important use cases involved with these scenarios.

    Imre Pühvel supported this idea  · 
  4. 47 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Imre Pühvel commented  · 

    Could it be support for this is dependent on the provider? I expected this to work and i believe it has been in some case, but now I experience built-in "Billing Reader" NOT being applied via nested groups.

    Imre Pühvel supported this idea  · 
  5. 5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Storage » Client Libraries  ·  Flag idea as inappropriate…  ·  Admin →
    Imre Pühvel supported this idea  · 
  6. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Azure Cosmos DB » SQL API  ·  Flag idea as inappropriate…  ·  Admin →
    Imre Pühvel shared this idea  · 
  7. 1,384 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    84 comments  ·  Storage » Tables  ·  Flag idea as inappropriate…  ·  Admin →
    Imre Pühvel supported this idea  · 
  8. 310 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Storage » General  ·  Flag idea as inappropriate…  ·  Admin →
    Imre Pühvel supported this idea  · 
  9. 1,835 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    74 comments  ·  Data Factory  ·  Flag idea as inappropriate…  ·  Admin →

    We want to share the great news that ADF has been added to the list of “Trusted Azure service” for Azure Key Vault and Azure Storage (blob & ADLS Gen2)!! Now you can enable “Allow trusted Microsoft services” on AKV and Azure Storage for better network security, and your ADF pipelines will continue to run. There are two caveats to pay attention to: (1) In order for ADF to be considered as one of the “Trusted Microsoft services” you need to use MSI to authenticate to AKV or Azure Storage in the linked service definition, and (2) If you are running Mapping Data Flow activity – “Trusted Azure service” is not supported for Data Flow just yet and we are working hard on it.

    What is coming up? Here are the additional enhancements we are making for better network security:
    - Static IP range for Azure Integration Runtime so that…

    Imre Pühvel supported this idea  · 
  10. 430 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Azure Cosmos DB » Management  ·  Flag idea as inappropriate…  ·  Admin →

    The ability to rename databases and collections is not currently something that is in our road map.

    Currently the way to accomplish this task in Cosmos DB is to create a new collection with the changed name then use bulk exec or change feed to populate it.

    Thanks for your request and input on this. We may consider this for a future planning cycle.

    thanks.

    Imre Pühvel commented  · 

    It doesn't even have to be a true rename of the same resource (which obviously could be complicated), but some tested comfortable migration automation, with suitable disclaimer regarding risks and most likely a small downtime is expected., would significantly reduce possible mishaps during manual resource reorganization.

    Imre Pühvel supported this idea  · 
  11. 18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Data Factory  ·  Flag idea as inappropriate…  ·  Admin →
    Imre Pühvel supported this idea  · 
    Imre Pühvel commented  · 

    Yes, please, my pipelines turn red every time a new customer registers (each has their own container for data separation). Currently I have to create a dummy "_letsMakeContainerNotEmpty.txt" file each time a provision a new container and ignore this in processing logic. This feels dirty.

  12. 147 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Azure Cosmos DB » SQL API  ·  Flag idea as inappropriate…  ·  Admin →
    Imre Pühvel supported this idea  · 
  13. 231 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Azure Cosmos DB » SQL API  ·  Flag idea as inappropriate…  ·  Admin →
    Imre Pühvel supported this idea  · 
  14. 417 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Azure Cosmos DB » SQL API  ·  Flag idea as inappropriate…  ·  Admin →
    Imre Pühvel supported this idea  · 
  15. 253 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Azure Cosmos DB » Other  ·  Flag idea as inappropriate…  ·  Admin →
    Imre Pühvel supported this idea  · 
  16. 18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Signup and Billing  ·  Flag idea as inappropriate…  ·  Admin →
    Imre Pühvel supported this idea  · 
  17. 148 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Signup and Billing  ·  Flag idea as inappropriate…  ·  Admin →
    Imre Pühvel supported this idea  · 
  18. 427 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    20 comments  ·  Signup and Billing  ·  Flag idea as inappropriate…  ·  Admin →
    Imre Pühvel supported this idea  · 
  19. 262 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  16 comments  ·  Signup and Billing  ·  Flag idea as inappropriate…  ·  Admin →
    Imre Pühvel supported this idea  · 
  20. 7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Storage » Portal  ·  Flag idea as inappropriate…  ·  Admin →
    Imre Pühvel commented  · 

    Current Cache-Control headers per blob are really cumbersome to change should application caching needs and policies change (and they do). In my project I have never needed to tailor caching for individual blobs, but to apply the same policy to ALL blobs of a similar meaning. Such blobs are usually organized into same containers/accounts. It seems like a common need.

    Current solution to enumerate all blobs in all containers and change their Cache-Control header would require custom scripting every time. Should you have millions of blobs this takes a lot of operations to bounce between Azure Storage and client. Getting overview and verification of Cache-Control settings once again requires another one-by-one enumeration of those millions of blobs.

    I acknowledge that per-blob granularity can be useful for many scenarios but I suggest a fallback to be implemented where the first existing Cache-control header is passed by examining:
    * blob
    * container
    * account

    Temporary workaround could be if Azure Storage Explorer would provide a tested and optimized command to apply a new Cache-Control header to all blobs in blob container .

    Imre Pühvel supported this idea  · 
← Previous 1

Feedback and Knowledge Base