You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-developer-cli/pipeline-github-actions.md
+54-28Lines changed: 54 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,9 @@
1
1
---
2
2
title: Configure a pipeline using GitHub Actions
3
-
description: Learn how to create a pipeline and push updates using GitHub Actions and the Azure Developer CLI
3
+
description: Learn how to create a pipeline and push updates using GitHub Actions and the Azure Developer CLI.
4
4
author: alexwolfmsft
5
5
ms.author: alexwolf
6
-
ms.date: 05/12/2025
6
+
ms.date: 07/29/2025
7
7
ms.service: azure-dev-cli
8
8
ms.topic: how-to
9
9
ms.custom: devx-track-azdevcli, build-2023
@@ -18,12 +18,14 @@ In this article, you'll learn how to use the Azure Developer CLI (`azd`) to crea
18
18
19
19
## Prerequisites
20
20
21
-
-[Install the Azure Developer CLI](install-azd.md).
22
-
-[Visual Studio Code](https://code.visualstudio.com/download) installed.
21
+
-[Install the Azure Developer CLI](install-azd.md)
22
+
-[Visual Studio Code](https://code.visualstudio.com/download) (optional, for editing files)
23
+
- A GitHub account
24
+
- An Azure subscription
23
25
24
26
## Initialize the template
25
27
26
-
This example uses the [Hello-AZD](https://github.com/azure-samples/hello-azd) template, but you can follow these steps for any template that includes a pipeline definition file (typically found in the `.github` or `.azdo` folders).
28
+
This example uses the [Hello-AZD](https://github.com/azure-samples/hello-azd) template, but you can follow these steps for any `azd`template that includes a pipeline definition file (typically found in the `.github` or `.azdo` folders).
27
29
28
30
1. In an empty directory, initialize the `hello-azd` template:
29
31
@@ -33,7 +35,7 @@ This example uses the [Hello-AZD](https://github.com/azure-samples/hello-azd) te
33
35
34
36
1. When prompted, enter a name for the environment, such as *helloazd*.
35
37
36
-
###Create a pipeline using GitHub Actions
38
+
## Create a pipeline using GitHub Actions
37
39
38
40
Follow these steps to create and configure a pipeline:
39
41
@@ -43,7 +45,26 @@ Follow these steps to create and configure a pipeline:
43
45
azd pipeline config
44
46
```
45
47
46
-
1. Provide the requested GitHub information.
48
+
1. When prompted to select a provider, choose **GitHub**.
49
+
50
+
```output
51
+
? Select a provider: [Use arrows to move, type to filter]
52
+
> GitHub
53
+
Azure DevOps
54
+
```
55
+
56
+
1. Select your desired Azure subscription and region.
57
+
58
+
1. When prompted to configure your remote repository, choose **Create a new private GitHub repository**. If you have an existing project you'd like to use, you can also choose **Select an existing GitHub project**.
59
+
60
+
```azdeveloper
61
+
? How would you like to configure your git remote to GitHub? [Use arrows to move, type to filter]
62
+
Select an existing GitHub project
63
+
> Create a new private GitHub repository
64
+
Enter a remote URL directly
65
+
```
66
+
67
+
1. Enter a name for the new repository.
47
68
48
69
1. When prompted to commit and push your local changes to start a new GitHub Actions run, enter `y`.
49
70
@@ -62,51 +83,56 @@ Follow these steps to create and configure a pipeline:
62
83
63
84
:::image type="content" source="media/configure-devops-pipeline/github-workflow.png" alt-text="Screenshot of GitHub workflow running.":::
64
85
65
-
### Push a code change
86
+
## Test the pipeline with a code change
66
87
67
88
1. In the project's `/src/components/pages` directory, open `Home.razor`.
68
-
2. Locate the `Hello AZD!` header text near the top of the file.
69
-
3. Change the text to `Hello, pipeline!`.
70
-
4. Save the file.
71
-
5. Commit and push your change. This triggers the GitHub Actions pipeline to deploy the update.
89
+
1. Locate the `Hello AZD!` header text near the top of the file.
90
+
1. Change the text to `Hello, pipeline!`.
91
+
1. Save the file.
92
+
1. Commit and push your change. This action triggers the GitHub Actions pipeline to deploy the update.
72
93
73
94
:::image type="content" source="media/configure-devops-pipeline/commit-changes-to-github.png" alt-text="Screenshot of steps required to make and commit change to test file.":::
74
95
75
-
6. In your browser, open your project's GitHub repository to see:
96
+
1. In your browser, open your project's GitHub repository to see:
76
97
- Your commit
77
-
- The commit from GitHub Actions being set up
98
+
- The commit from GitHub Actions setup
78
99
79
100
:::image type="content" source="media/configure-devops-pipeline/committed-changes-in-github-repo.png" alt-text="Screenshot of your committed change in GitHub.":::
80
101
81
-
7. Select **Actions** to see the test update reflected in the workflow.
102
+
1. Select **Actions** to see the test update reflected in the workflow.
82
103
83
104
:::image type="content" source="media/configure-devops-pipeline/github-workflow-after-test-update.png" alt-text="Screenshot of GitHub workflow running after test update.":::
84
105
85
-
8. To view the update, visit the web frontend URL.
106
+
1. To view the deployed update, visit the web frontend URL provided in the `azd` output.
86
107
87
-
###Use `azd` as a GitHub Action
108
+
## Use `azd` as a GitHub Action
88
109
89
-
Install [`azd` as a GitHub Action](https://aka.ms/azd-gha). To use it, add the following to `.github/workflows/azure-dev.yml`:
110
+
You can install `azd` as a GitHub Action using the [setup-azd action](https://github.com/Azure/setup-azd). To use it, add the following to your `.github/workflows/azure-dev.yml` file:
|[Azure Kubernetes Service](../../tools/azure-aks.md)| List Azure Kubernetes Service clusters. |
28
29
|[Azure Load Testing](../../tools/azure-load-testing.md)| Create, run, and see load testing. |
30
+
|[Azure MCP tool](../../tools/azure-mcp-tool.md)| Discover and manage available Azure MCP Server tools. |
29
31
|[Azure Monitor](../../tools/monitor.md)| Query Azure Monitor logs and metrics. |
30
32
|[Azure Native ISV](../../tools/azure-native-isv.md)| Work with Azure Native ISV services, including Datadog integration for monitoring and observability. |
33
+
| [Azure Quick Review CLI](../../tools/azure-compliance-quick-review.md) | Generate compliance and security reports for Azure resources.
31
34
|[Azure RBAC](../../tools/azure-rbac.md)| View and manage Azure role-based access control assignments. |
32
35
|[Azure Service Bus](../../tools/service-bus.md)| Work with Azure Service Bus messaging services. |
33
36
|[Azure SQL](../../tools/azure-sql.md)| Work with Azure SQL Database servers, databases, firewall rules, and elastic pools. |
# Azure Quick Review CLI tools for the Azure MCP Server
15
+
16
+
The Azure MCP Server allows you to execute Azure Quick Review (azqr) commands using natural language prompts. This enables you to generate compliance and security reports for your Azure resources to identify non-compliant configurations and areas for improvement without needing to remember specific command syntax.
17
+
18
+
[Azure Quick Review CLI (azqr)](https://github.com/Azure/azqr) is a powerful command-line interface (CLI) tool that specializes in analyzing Azure resources to ensure compliance with Azure's best practices and recommendations. Its main objective is to offer users a comprehensive overview of their Azure resources, allowing them to easily identify any non-compliant configurations or areas for improvement.
The Azure MCP Server can execute Azure Quick Review CLI commands to generate compliance and security reports for Azure resources. This helps identify non-compliant configurations and areas for improvement in your Azure environment.
25
+
26
+
**Example prompts** include:
27
+
28
+
- **Scan subscription**: "Generate compliance report for my subscription"
29
+
- **Scan resource group**: "Run security assessment for production resource group"
30
+
- **Quick review**: "Check my subscription for compliance issues"
31
+
- **Security scan**: "scan resources in dev-rg for security problems"
32
+
- **Generate report**: "Create compliance report for subscription abc123 and resource group web-apps"
33
+
34
+
| Parameter | Required or optional | Description |
35
+
|-----------|-------------|-------------|
36
+
| **Subscription** | Required | The Azure subscription ID or name to scan for compliance issues. |
37
+
| **Resource group** | Optional | The name of the Azure resource group to scope the scan to a specific resource group. |
38
+
39
+
## Related content
40
+
41
+
- [What are the Azure MCP Server tools?](index.md)
42
+
- [Get started using Azure MCP Server](../get-started.md)
# Azure Developer CLI extension tools for the Azure MCP Server
15
+
16
+
The Azure MCP Server allows you to execute any Azure Developer CLI command using natural language prompts. You can perform application development, deployment, and management operations without needing to remember specific command syntax, parameters, or formatting.
17
+
18
+
[Azure Developer CLI (azd)](/azure/developer/azure-developer-cli/) is a developer-centric command-line interface (CLI) tool for creating Azure applications. It provides a set of developer-friendly commands that map to key stages in your workflow, from initializing a new project to deploying to Azure. For a complete list of Azure Developer CLI commands this tool can execute, see the [Azure Developer CLI reference documentation](/azure/developer/azure-developer-cli/reference).
The Azure MCP Server can execute Azure Developer CLI commands. This provides complete access to Azure application development and deployment operations through familiar command-line syntax.
25
+
26
+
**Example prompts** include:
27
+
28
+
- **Initialize a new project**: "Create a sample todo list app with NodeJS and MongoDB"
29
+
- **Deploy application**: "Deploy my application to Azure"
30
+
- **Manage environments**: "Show me my azd environments"
31
+
- **Monitor application**: "Check the status of my deployed application"
32
+
- **Template operations**: "List available azd templates"
33
+
34
+
| Parameter | Required or optional | Description |
35
+
|-----------|-------------|-------------|
36
+
| **Command** | Required | The Azure Developer CLI command to execute (without the 'azd' prefix). For a complete list of Azure Developer CLI commands, see the [Azure Developer CLI reference documentation](/azure/developer/azure-developer-cli/reference). |
37
+
38
+
## Related content
39
+
40
+
- [What are the Azure MCP Server tools?](index.md)
41
+
- [Get started using Azure MCP Server](../get-started.md)
# Azure MCP tools management for the Azure MCP Server
15
+
16
+
The Azure MCP Server provides tools to discover and manage the available Azure tools within the server. You can list all available tools using natural language prompts without remembering specific command syntax.
The Azure MCP Server can list all available tools and their capabilities. This helps you discover what Azure services and operations you can manage through the MCP server.
24
+
25
+
**Example prompts** include:
26
+
27
+
- **List all tools**: "Show me all available Azure MCP tools"
28
+
- **Discover capabilities**: "What tools are available in the Azure MCP server?"
29
+
- **View tool inventory**: "List all Azure tools I can use"
30
+
- **Check available services**: "What Azure services can I manage with MCP?"
31
+
- **Find tools**: "Show me what Azure operations are available"
32
+
33
+
| Parameter | Required or optional | Description |
34
+
|-----------|-------------|-------------|
35
+
| None | N/A | This command requires no parameters and lists all available tools. |
36
+
37
+
38
+
## Related content
39
+
40
+
- [What are the Azure MCP Server tools?](index.md)
41
+
- [Get started using Azure MCP Server](../get-started.md)
42
+
- [Azure MCP Server GitHub repository](https://github.com/Azure-Samples/azure-mcp-server)
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments