bcgov / Cloud-Pathfinder-Azure

Apache License 2.0
0 stars 0 forks source link

New Project Set Onboarding Process Documentation #129

Open AErmie opened 2 months ago

AErmie commented 2 months ago

As part of onboarding a new Project Set, we need to create a Standard Operating Procedure (SOP) that includes the following:

[!NOTE] We should also look into how we can automate some of this process. Currently, it requires someone emailing our Microsoft Technical Account Manager (TAM) with a list of Subscription IDs.

Even though Microsoft's process itself is not automated either, could we programmatically collect the new Subscription IDs and send an automated email on a weekly basis?

Acceptance Criteria

AErmie commented 2 months ago

There is a Subscriptions Get API, but it does not have any relevant information about associated Support Plan. Additionally, there is a Microsoft Azure CLI 'support' Extension, but again, it does not have any properties that would show the type of Support Plan available.

wrnu commented 2 months ago

I think the Unified support makes this all a bit strange. We should put this on our list of things to talk with Barry about

mitovskaol commented 1 month ago

@abibat-adesina @AErmie Please make sure the Azure tech docs are close as possible to the AWS tech docs i.e. have the same structure and same content just Azure specific. Also, please avoid copy-pasting content from the vendor website, just include the link.

AErmie commented 4 weeks ago

As part of onboarding a new Project Set, our documentation states:

Once approved, your Project Set will be provisioned, followed up by an email sent to the Product Owner and Technical Lead(s) once the provisioning is complete.

This part of the process is (or should be) automated. This means we could modify this process to also email Microsoft with the new Subscription IDs to enable for Unified Support.