Background

Instead of providing service principals and secrets directly in the ansible playbooks there is a better way.  Attaching System Assigned Identity or User Assigned Identities to resources allows for security permissions between resources without having to embed the secrets or tokens in the ansible playbooks.

User Stories

Format: "as a <type of user> I want <some goal> so that <some reason>"

Supporting documentation

<include links to technical docs, diagrams, etc>

Ready-Ready

https://docs.google.com/document/d/1dBW492UfCR5JxUvcx6efjYP_ibCdiwGONS-sxDb_SPU/edit# 

Complete Ready-Ready checklist

Definition of Done

Should be agreed upon per team; add/remove/update to reflect:{}

• CI is running, tests are automated and merged and successful
• DEV upstream code & tests merged
• DEV upstream documentation merged
• DEV downstream build attached to advisory
• QE - Test plans documented and attached to epic (or link to source)
• QE - automated tests merged and passing
• Docs - Downstream documentation is merged
• PM - all acceptance criteria are met (note: we want to start using the AC specific field, but please fill out below in the meantime)

Note: please also fill out the 'Acceptance Criteria' to indicate functional criteria aka scope, specific to this issue, that should be met in order to 'accept' the work to consider complete.