1. Onboarding meeting with GIS

2. Create Document (i.e.) TAD, NSM

3. Get Azure DevOps project

4. Deploy and test Dev

5. Get and Setup Dev Environment

6. Design with OpenAPI specification

7. Provide the Prerequisites for UAT onboarding

8. Post UAT Onboarding, deploy and test in UAT

9. Provide the onboarding deploy and test in PROD

10. Post PRD onboarding deploy and test in PRD

11. Post Onboarding meeting with GIS

To get onboarded to Global Shared APIM service, following information is required to be sent at this link (Only accessible for Sodexo users)

1. Business line Name

2. Project Name (Resource group naming convention)

3. Azure DevOps Project (if Azure DevOps project is not there, please raise a Stepso Ivanti request under category – “Global Datacentres & Cloud Services – License for Azure DevOps”

4. Service Principal (Rights granted on your resource group)

   • Please get a new service principal scoped to a resource group. To get a new service principal, please raise a Stepso Ivanti request with the Identity team

5. BU Managers AD Group (To access your resource group with Azure Portal)

6. BU Developers AD Group (To access your resource group with Azure Portal)

7. API Management Product Name (Your product which will contains your APIs)

8. BU Manager email (API consumption alerting)

9. RPS (Request Per Second) assumption of your APIs (Small, Medium, Large in terms of T-shirt size)

10. SRAQ Information

11. Register Client apps in Azure AD for OAuth 2.0

    1. For OAuth 2.0, we must register both (the client system and the backend API) as applications in Azure AD. Registration of backend API (if it is Rest API) is done by Global Shared APIM team but the client system registration will have to be done by the BU project team.

    2. Once registration of client system is completed, Azure AD team will share client-id and client-secret which will be used for authentication when calling backend API. Apart from client-id & client-secret client systems also need subscription key to be passed as a header in the API request call.

12. BU Project team should identify and provide network flows needed by backend API to communicate with Global Shared APIM