Azure Product Excellence (APEX) name change to Cloud Product Excellence (CPEX)

[ladonnaq]

1. Group Aliases

• azsdkapex (create new security group and include the old one for 6 months) new security group created with alias "azsdkcpex".
• plrsdk@microsoft.com (delete, older not needed)

2. AKA links that need to be updated:

• https://aka.ms/azsdk/apex/dashboard-admin (Azure Devops dashboard)
• https://aka.ms/sdk-apex
• https://aka.ms/azsdk/APEX/exception
• https://aka.ms/azsdk/APEX/GASignoff
• https://aka.ms/azsdk/APEX/PubPreviewSignoff
• https://aka.ms/azsdk/apex/launch-criteria

3. Docs that need to be updated:

• https://eng.ms/docs/products/azure-developer-experience/onboard/requirements
• https://eng.ms/docs/products/azure-developer-experience/onboard/request-apex-sign-off
• https://eng.ms/docs/products/azure-developer-experience/onboard/request-exception
• https://eng.ms/docs/products/azure-developer-experience/onboard
• https://eng.ms/docs/products/azure-developer-experience/onboard/informational-meeting
• All descriptions of the Azure SDK requirements in Cloud Lifecycle - https://vnext.s360test.msftcloudes.com/kpidirectory?peopleBasedNodes=lorifraleigh_team&global=@LORIFRALEIGH%2BLori%20Fraleigh%20(LORIFRALEIGH)&selectedTab=myKPIDirectory&filters=%5B%5D&actionItemId=48de128c-431e-4e67-9914-91b1394d4e31

4. Release Planner

• All onboarding email templates
• Message that notifies user that their product is out of scope for CPEX requirements (onboarding feature)
• Create a release plan revised UI - Improvements to the "create a release plan" experience to ensure process adherence, automate decision-making, and enhance data integrity  #6262

5. Azure Devops - @maririos @praveenkuttappan I'm uncertain about the impact on automation, so we should discuss the best approach. There are tabs and group names that need to be renamed, such as the APEX data tab. For data fields, it might be easier to change the label name in the ADO template rather than creating new data fields. For example the isAPEX data field could remain isAPEX in the back-end but the data label on the ADO epic could be renamed to isCPEX.

6. Engagement Experience/Release Planner PowerBI Report - The APEX visuals will need to be updated.