Hmm., thanks for the demo for clicking through, however you dont show that it actually works. Since Managed IDs have to use a Host Agent, where do you show your azure-pipelines.xml with the pool settings for execution? As well, are you really using this Managed ID Service Connector? with what Task ? AzureCLI@2 ? or are you just doing "bash" and then doing your own "az login --identity -u
do you know if we can make an image of this VM and supply to vmImage key in pipeline yml to spin it up on demand. i dont want to keep a self hosted VM up all the time just for CI/CD
Thanks Houssem for the video.. one question, when and why we should use system assigned managed identity over user assigned managed identity? Is there any specific individual usage or benefit of these two?
System assigned Managed Identity is scoped exclusively to the entity that was created. Meaning, if you create a VM inside Azure and use System Assigned Identity, that Identity will only be relevant for that VM. An User Assigned Managed Identity can group a collection of entities, and that User Assigned Identity must be manually deleted even if all of those resources are dropped. A system Assigned is only valid for a single entity. User Assigned can be used for multiple entities, if that's how you assign them.
Is there a way to utilize Managed ID without building your own Self Agent VM IASS ?
Hmm.,
thanks for the demo for clicking through, however you dont show that it actually works.
Since Managed IDs have to use a Host Agent, where do you show your azure-pipelines.xml with the pool settings for execution? As well, are you really using this Managed ID Service Connector? with what Task ? AzureCLI@2 ? or are you just doing "bash" and then doing your own "az login --identity -u
Exactly my question.
Video stopped exactly where the topic of the video was supposed to start .
Felt much the same
do you know if we can make an image of this VM and supply to vmImage key in pipeline yml to spin it up on demand. i dont want to keep a self hosted VM up all the time just for CI/CD
Thanks Houssem for the video.. one question, when and why we should use system assigned managed identity over user assigned managed identity? Is there any specific individual usage or benefit of these two?
System assigned Managed Identity is scoped exclusively to the entity that was created. Meaning, if you create a VM inside Azure and use System Assigned Identity, that Identity will only be relevant for that VM.
An User Assigned Managed Identity can group a collection of entities, and that User Assigned Identity must be manually deleted even if all of those resources are dropped. A system Assigned is only valid for a single entity. User Assigned can be used for multiple entities, if that's how you assign them.
@@ryanshannon6963 Thanks Ryan.. Appreciate your time for this explanation..