GitHub secret name in the article is different from the YAML config in azureml-examples

[rtrad89]

The article instructs to create a GitHub repository secret with the name AZURE_CREDENTIALS. However, in azureml-examples that is to be forked and cloned, the secret name in YAML is AZUREML_CREDENTIALS. This causes the jobs to fail with the message:

Run azure/login@v1
Error: Login failed with Error: Using auth-type: SERVICE_PRINCIPAL. Not all values are present. Ensure 'client-id' and 'tenant-id' are supplied.. Double check if the 'auth-type' is correct. Refer to https://github.com/Azure/login#readme for more information.

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 70a73a03-d004-f16e-95ad-11732b0160e2
• Version Independent ID: a368a780-d2c3-863a-9c7f-1fcb1d07d7a0
• Content: GitHub Actions for CI/CD - Azure Machine Learning
• Content Source: articles/machine-learning/how-to-github-actions-machine-learning.md
• Service: machine-learning
• Sub-service: mlops
• GitHub Login: @juliakm
• Microsoft Alias: jukullam

[TPavanBalaji]

@rtrad89 Thanks for your feedback! We will investigate and update as appropriate.

[AjayBathini-MSFT]

@rtrad89 Thank you for your feedback! I'd recommend working closer with our support team via an [Azure support request] (https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request). Or you can leverage our Q&A forum by posting your issue there so our community, and MVPs can further assist you in troubleshooting this issue or finding potential workarounds. [Teams Q&A forum] (https://docs.microsoft.com/en-us/answers/topics/46488/office-teams-windows-itpro.html) for technical questions about the configuration and administration of Microsoft Teams on Windows. [Microsoft Teams Community forum] (https://answers.microsoft.com/en-us/msteams/forum?sort=LastReplyDate&dir=Desc&tab=All&status=all&mod=&modAge=&advFil=&postedAfter=&postedBefore=&threadType=All&isFilterExpanded=false&page=1) Thank you for your time and patience throughout this issue.