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
{{ message }}
Repository navigation
Commit 0d408ce
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: README.md
+72-1Lines changed: 72 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,13 @@
1
1
# Azure Login Action
2
2
3
3
-[Azure Login Action](#azure-login-action)
4
+
-[Supported Versions](#supported-versions)
5
+
-[Version Selection](#version-selection)
6
+
-[Major-version tag](#major-version-tag)
7
+
-[Exact version tag](#exact-version-tag)
8
+
-[Branch reference](#branch-reference)
9
+
-[Commit SHA](#commit-sha)
10
+
-[Security Updates](#security-updates)
4
11
-[Input Parameters](#input-parameters)
5
12
-[`client-id`](#client-id)
6
13
-[`subscription-id`](#subscription-id)
@@ -48,6 +55,70 @@ Azure Login Action supports different ways of authentication with Azure.
48
55
> [!WARNING]
49
56
> Avoid using managed identity login on self-hosted runners in public repositories. Managed identities enable secure authentication with Azure resources and obtain Microsoft Entra ID tokens without the need for explicit credential management. Any user can open pull requests against your repository and access your self-hosted runners without credentials. See more details in [self-hosted runner security](https://docs.github.com/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners#self-hosted-runner-security).
50
57
58
+
## Supported Versions
59
+
60
+
Azure Login follows a major-version support model.
61
+
62
+
| Version | Status |
63
+
| --- | --- |
64
+
| v3 | Supported |
65
+
| v2 | Maintenance mode (security fixes only) |
66
+
| v1 | End of Life (EOL) |
67
+
68
+
New features are released only to supported versions. Security fixes are released to supported versions and versions in maintenance mode.
69
+
70
+
Customers are strongly encouraged to use the latest v3 release.
71
+
72
+
## Version Selection
73
+
74
+
GitHub Actions users can reference Azure Login using several forms.
75
+
76
+
### Major-version tag
77
+
78
+
```yaml
79
+
uses: azure/login@v3
80
+
```
81
+
82
+
Receives compatible updates, including security fixes, released to the referenced major version.
83
+
84
+
### Exact version tag
85
+
86
+
```yaml
87
+
uses: azure/login@v2.4.0
88
+
```
89
+
90
+
Remains pinned to that specific release and does not automatically receive future fixes or updates.
91
+
92
+
### Branch reference
93
+
94
+
```yaml
95
+
uses: azure/login@master
96
+
```
97
+
98
+
Receives updates from the referenced branch. For stable workflows, use a supported major-version tag or pin to a full-length commit SHA.
99
+
100
+
### Commit SHA
101
+
102
+
```yaml
103
+
uses: azure/login@<full-length-commit-sha>
104
+
```
105
+
106
+
Remains pinned to that commit and does not automatically receive future fixes or updates.
107
+
108
+
## Security Updates
109
+
110
+
Security fixes are released to supported versions and versions in maintenance mode. Customers using exact version tags or commit SHA references must explicitly upgrade to a patched release to receive security fixes.
0 commit comments