Skip to content

Commit e9b3707

Browse files
committed
feat: using tips
1 parent 66f373d commit e9b3707

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

_posts/en/2025-03-05-integrating-backstage-azure-devops.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,11 +36,13 @@ I'll keep a repository on my GitHub with the Backstage code resulting from these
3636
9. [Final Test](#final-test)
3737
10. [Conclusion](#conclusion)
3838

39-
💡 **Note**: Having Entra ID as an IDP is not a prerequisite for working with Azure DevOps. However, it is common for both solutions to be used in a Microsoft environment.
39+
> **Note**: Having Entra ID as an IDP is not a prerequisite for working with Azure DevOps. However, it is common for both solutions to be used in a Microsoft environment.
40+
{: .prompt-tip }
4041

4142
For this post, I created a new project in Azure DevOps called Backstage, where we will store our Backstage template, Terraform code, and the yaml file to create our pipeline.
4243

43-
⚠️ **Attention**: I will assume that you already know how to create a project, repository, and use the minimum necessary git commands.
44+
>⚠️**Attention**: I will assume that you already know how to create a project, repository, and use the minimum necessary git commands.
45+
{: .prompt-warning}
4446

4547
[In this link](https://backstage.io/docs/integrations/azure/locations) you can check the Backstage documentation for this integration. Backstage supports the use of managed identity, service principal, and PAT. For the purpose of this post, I will use PAT as it is simpler.
4648

0 commit comments

Comments
 (0)