Stanley Merkx

My feedback

  1. 29 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Automation » PowerShell cmdlets  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Stanley Merkx commented  · 

    If this could be integrated with the "Source Control" feature: even better.

    Edits committed to the repository, through pull-request, peer-review, etc, should be signed on import using a certificate imported from a configurable keyvault or (mvp) using an automation 'certificate' shared resource.

    We can then enforce that runbooks can only be edited from the repository. Any edits done in the portal will invalidate the signature causing the runbook to fail after such an edit.

  2. 60 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Automation » User Experience  ·  Flag idea as inappropriate…  ·  Admin →
    Stanley Merkx supported this idea  · 
    An error occurred while saving the comment
    Stanley Merkx commented  · 

    You could in fact do this quite easily from Powershell:

    $JobParameters = (Get-AzureRmAutomationJob -Id $JobId -AutomationAccountName $AutomationAccountName -ResourceGroupName $AutomationResourceGroupName).JobParameters

    Start-AzureRmAutomationRunbook -AutomationAccountName $AutomationAccountName -ResourceGroupName $AutomationResourceGroupName -Name $RunbookName -Parameters $JobParameters

    But an integrated option in the portal would be greatly appreciated :-).

    But given the fact that this idea has been "under review" for more than 4 years, I guess it's not going to happen...

  3. 2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Automation  ·  Flag idea as inappropriate…  ·  Admin →
    Stanley Merkx shared this idea  · 
  4. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Automation  ·  Flag idea as inappropriate…  ·  Admin →
    Stanley Merkx shared this idea  · 
  5. 122 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Automation » PowerShell cmdlets  ·  Flag idea as inappropriate…  ·  Admin →
    Stanley Merkx supported this idea  · 
    An error occurred while saving the comment
    Stanley Merkx commented  · 

    Why not simply add these attributes to $PSPrivateMetadata ??

    Should be relatively simple to implement and easy to retrieve without additional cmdlets...

  6. 1,196 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    21 comments  ·  Networking » Bastion  ·  Flag idea as inappropriate…  ·  Admin →
    Stanley Merkx supported this idea  · 
  7. 2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure mobile app  ·  Flag idea as inappropriate…  ·  Admin →
    Stanley Merkx shared this idea  · 
  8. 15 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Azure Resource Manager  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Stanley Merkx commented  · 

    Hmm, so setting the policy type to "indexed" fixed the policy: it now only applies to taggable resources so it's no longer non-compliant. IMHO that is just a workaround as these resources may still show up in billing/usage reports and should be recognisable by individual tags...

    Stanley Merkx supported this idea  · 
    An error occurred while saving the comment
    Stanley Merkx commented  · 

    Please make ALL resources taggable.

    I have recently implemented a policy to copy tag values from the resource group onto individual resources within the RG (See https://docs.microsoft.com/en-us/azure/governance/policy/concepts/definition-structure#policy-function-examples), but when a group contains resources that are not taggable, the policy is shown as non-compliant for that subscription.

  9. 12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Stanley Merkx commented  · 

    Similar problem between portal and Powershell: the portal (mostly) treats Tags as case insensitive, while manipulation of Tags from Powershell is case sensitive. Make your mind up about how to treat Tags and stick to it...

  10. 5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Virtual Machines » Windows  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Stanley Merkx commented  · 

    Agreed, but Get-AzueRmVMSize should show more attributes than only support for accelerated networking. See also my request at https://feedback.azure.com/forums/34192--general-feedback/suggestions/35068363-get-azurermvmsize-should-show-additional-capabilit

    (which bt the way has also not received any feedback from MS).

  11. 7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  (General Feedback) » Other  ·  Flag idea as inappropriate…  ·  Admin →
    Stanley Merkx shared this idea  · 
  12. 173 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    24 comments  ·  Virtual Machines » Windows  ·  Flag idea as inappropriate…  ·  Admin →
  13. 4 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Virtual Machines » Windows  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Stanley Merkx commented  · 

    And while we're at it: why does a marketplace image need a "plan" property which seemingly contains the same info as already present in the "imagereference" section?

    This too makes it very difficult to have a single template that works for standard images and for marketplace images.

    And there should be to accept an EULA from within a template: that would prevent "Error: Code=MarketplacePurchaseEligibilityFailed". Obviously this should be done in such a way that it doesn't interfere with regular non-marketplace images.

    Stanley Merkx shared this idea  · 
  14. 37 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Azure Governance » Azure Policy  ·  Flag idea as inappropriate…  ·  Admin →
    Stanley Merkx supported this idea  · 
  15. 101 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Azure Resource Manager  ·  Flag idea as inappropriate…  ·  Admin →
  16. 1,916 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We’re currently evaluating an option that will provide the functionality offered by nested groups, but removes the complexity nested groups adds. We appreciate your patience on this ask and want to ensure we deliver a solution that benefits all of our customers. Below are use cases that we’d like for you to stack rank, with #1 being priority for you. We thank you for the continued comments and feedback.

    Use case A: nested group in a cloud security group inherits apps assignment
    Use case B: nested group in a cloud security group inherits license assignment
    Use case C: nesting groups under Office 365 groups

    Stanley Merkx supported this idea  · 
  17. 10 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Virtual Machines  ·  Flag idea as inappropriate…  ·  Admin →
    Stanley Merkx supported this idea  · 

Feedback and Knowledge Base