Florian Scheepstra

My feedback

  1. 9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Cache » Azure Redis Cache  ·  Flag idea as inappropriate…  ·  Admin →
    Florian Scheepstra supported this idea  · 
  2. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Cache » Azure Redis Cache  ·  Flag idea as inappropriate…  ·  Admin →
    Florian Scheepstra supported this idea  · 
  3. 287 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    45 comments  ·  Azure Monitor-Application Insights » SDK  ·  Flag idea as inappropriate…  ·  Admin →
    Florian Scheepstra supported this idea  · 
  4. 127 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Florian Scheepstra supported this idea  · 
  5. 271 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  20 comments  ·  Azure Resource Manager  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Florian Scheepstra commented  · 

    Some sort of a solution would be actually required when using templateLinks in ARM files which you have under sourcecontrol and push out via the Azure DevOps pipelines.
    Currently it is required to use a StorageAccount but if we could circumvent this need in the pipeline it would make the whole deployment much easier and less fragile, perhaps even more secure.

    One possible solution is to merge the templates before pushing it to Azure. This could even be a new specific Task so the current Resource Manager task wouldn't need any changes...

Feedback and Knowledge Base