As a Ministry Team, I want a "Non-Application" subscription, so that I have an option for services not using the typical project set structure.
Context: We might become responsible for managing Azure subscriptions that aren't app related, such as logging, Defender/Sentinel, etc. These wouldn't require some core components of the Landing Zone such as networking, and would benefit from a simpler structure, while still managed in our space.
Acceptance Criteria:
[ ] Define Non-Application subscriptions
[ ] Determine what should apply to them
[ ] Determine how to convert a non-app subscription to "regular", in case someone wants to start building an app in it.
[ ] Draw and Estimate backend work to build this feature.
[ ] List frontend elements that might need an update in the registry.
As a Ministry Team, I want a "Non-Application" subscription, so that I have an option for services not using the typical project set structure.
Context: We might become responsible for managing Azure subscriptions that aren't app related, such as logging, Defender/Sentinel, etc. These wouldn't require some core components of the Landing Zone such as networking, and would benefit from a simpler structure, while still managed in our space.
Acceptance Criteria: