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/active-directory/roles/admin-units-assign-roles.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,7 +50,7 @@ The following Azure AD roles can be assigned with administrative unit scope. Add
50
50
|[SharePoint Administrator](permissions-reference.md#sharepoint-administrator)| Can manage Microsoft 365 groups in the assigned administrative unit only. For SharePoint sites associated with Microsoft 365 groups in an administrative unit, can also update site properties (site name, URL, and external sharing policy) using the Microsoft 365 admin center. Cannot use the SharePoint admin center or SharePoint APIs to manage sites. |
51
51
|[Teams Administrator](permissions-reference.md#teams-administrator)| Can manage Microsoft 365 groups in the assigned administrative unit only. Can manage team members in the Microsoft 365 admin center for teams associated with groups in the assigned administrative unit only. Cannot use the Teams admin center. |
52
52
|[Teams Devices Administrator](permissions-reference.md#teams-devices-administrator)| Can perform management related tasks on Teams certified devices. |
53
-
|[User Administrator](permissions-reference.md#user-administrator)| Can manage all aspects of users and groups, including resetting passwords for limited admins within the assigned administrative unit only. |
53
+
|[User Administrator](permissions-reference.md#user-administrator)| Can manage all aspects of users and groups, including resetting passwords for limited admins within the assigned administrative unit only. Cannot currently manage users' profile photographs. |
54
54
|[<Custom role>](custom-create.md)| Can perform actions that apply to users, groups, or devices, according to the definition of the custom role. |
55
55
56
56
Certain role permissions apply only to non-administrator users when assigned with the scope of an administrative unit. In other words, administrative unit scoped [Helpdesk Administrators](permissions-reference.md#helpdesk-administrator) can reset passwords for users in the administrative unit only if those users do not have administrator roles. The following list of permissions are restricted when the target of an action is another administrator:
Copy file name to clipboardExpand all lines: articles/aks/tutorial-kubernetes-deploy-application.md
+28-27Lines changed: 28 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,36 +1,36 @@
1
1
---
2
-
title: Kubernetes on Azure tutorial - Deploy an application
2
+
title: Kubernetes on Azure tutorial - Deploy an application
3
3
description: In this Azure Kubernetes Service (AKS) tutorial, you deploy a multi-container application to your cluster using a custom image stored in Azure Container Registry.
4
4
services: container-service
5
5
ms.topic: tutorial
6
-
ms.date: 05/24/2021
7
-
6
+
ms.date: 01/04/2023
8
7
ms.custom: mvc, devx-track-azurepowershell
9
8
10
9
#Customer intent: As a developer, I want to learn how to deploy apps to an Azure Kubernetes Service (AKS) cluster so that I can deploy and run my own applications.
11
10
---
12
11
13
12
# Tutorial: Run applications in Azure Kubernetes Service (AKS)
14
13
15
-
Kubernetes provides a distributed platform for containerized applications. You build and deploy your own applications and services into a Kubernetes cluster, and let the cluster manage the availability and connectivity. In this tutorial, part four of seven, a sample application is deployed into a Kubernetes cluster. You learn how to:
14
+
Kubernetes provides a distributed platform for containerized applications. You build and deploy your own applications and services into a Kubernetes cluster and let the cluster manage the availability and connectivity. In this tutorial, part four of seven, you deploy a sample application into a Kubernetes cluster. You learn how to:
16
15
17
16
> [!div class="checklist"]
18
-
> * Update a Kubernetes manifest file
19
-
> * Run an application in Kubernetes
20
-
> * Test the application
17
+
>
18
+
> * Update a Kubernetes manifest file.
19
+
> * Run an application in Kubernetes.
20
+
> * Test the application.
21
21
22
-
In later tutorials, this application is scaled out and updated.
22
+
In later tutorials, you'll scale out and update your application.
23
23
24
-
This quickstart assumes a basic understanding of Kubernetes concepts. For more information, see [Kubernetes core concepts for Azure Kubernetes Service (AKS)][kubernetes-concepts].
24
+
This quickstart assumes you have a basic understanding of Kubernetes concepts. For more information, see [Kubernetes core concepts for Azure Kubernetes Service (AKS)][kubernetes-concepts].
25
25
26
26
> [!TIP]
27
-
> AKS clusters can use GitOps for configuration management. This enables declarations of your cluster's state, which are pushed to source control, to be applied to the cluster automatically. To learn how to use GitOps to deploy an application with an AKS cluster, see the tutorial [Use GitOps with Flux v2][gitops-flux-tutorial] and follow the [prerequisites for Azure Kubernetes Service clusters][gitops-flux-tutorial-aks].
27
+
> AKS clusters can use GitOps for configuration management. GitOp enables declarations of your cluster's state, which are pushed to source control, to be applied to the cluster automatically. To learn how to use GitOps to deploy an application with an AKS cluster, see the [prerequisites for Azure Kubernetes Service clusters][gitops-flux-tutorial-aks] in the [GitOps with Flux v2][gitops-flux-tutorial] tutorial.
28
28
29
29
## Before you begin
30
30
31
-
In previous tutorials, an application was packaged into a container image, this image was uploaded to Azure Container Registry, and a Kubernetes cluster was created.
31
+
In previous tutorials, you packaged an application into a container image, uploaded the image to Azure Container Registry, and created a Kubernetes cluster.
32
32
33
-
To complete this tutorial, you need the pre-created `azure-vote-all-in-one-redis.yaml` Kubernetes manifest file. This file was downloaded with the application source code in a previous tutorial. Verify that you've cloned the repo, and that you have changed directories into the cloned repo. If you haven't done these steps, and would like to follow along, start with [Tutorial 1 – Create container images][aks-tutorial-prepare-app].
33
+
To complete this tutorial, you need the pre-created `azure-vote-all-in-one-redis.yaml` Kubernetes manifest file. This file download was included with the application source code in a previous tutorial. Verify that you've cloned the repo and that you've changed directories into the cloned repo. If you haven't done these steps and would like to follow along, start with [Tutorial 1: Prepare an application for AKS][aks-tutorial-prepare-app].
34
34
35
35
### [Azure CLI](#tab/azure-cli)
36
36
@@ -48,37 +48,37 @@ In these tutorials, an Azure Container Registry (ACR) instance stores the contai
48
48
49
49
### [Azure CLI](#tab/azure-cli)
50
50
51
-
Get the ACR login server name using the [az acr list][az-acr-list] command as follows:
51
+
Get the ACR login server name using the [az acr list][az-acr-list] command.
52
52
53
53
```azurecli
54
54
az acr list --resource-group myResourceGroup --query "[].{acrLoginServer:loginServer}" --output table
55
55
```
56
56
57
57
### [Azure PowerShell](#tab/azure-powershell)
58
58
59
-
Get the ACR login server name using the [Get-AzContainerRegistry][get-azcontainerregistry] cmdlet as follows:
59
+
Get the ACR login server name using the [Get-AzContainerRegistry][get-azcontainerregistry] cmdlet.
The sample manifest file from the git repo cloned in the first tutorial uses the images from Microsoft Container Registry (*mcr.microsoft.com*). Make sure that you're in the cloned *azure-voting-app-redis* directory, then open the manifest file with a text editor, such as `vi`:
67
+
The sample manifest file from the git repo you cloned in the first tutorial uses the images from Microsoft Container Registry (*mcr.microsoft.com*). Make sure you're in the cloned *azure-voting-app-redis* directory, and then open the manifest file with a text editor, such as `vi`:
68
68
69
69
```console
70
70
vi azure-vote-all-in-one-redis.yaml
71
71
```
72
72
73
-
Replace *mcr.microsoft.com* with your ACR login server name. The image name is found on line 60 of the manifest file. The following example shows the default image name:
73
+
Replace *mcr.microsoft.com* with your ACR login server name. You can find the image name on line 60 of the manifest file. The following example shows the default image name:
Provide your own ACR login server name so that your manifest file looks like the following example:
81
+
Provide your own ACR login server name so your manifest file looks similar to the following example:
82
82
83
83
```yaml
84
84
containers:
@@ -90,7 +90,7 @@ Save and close the file. In `vi`, use `:wq`.
90
90
91
91
## Deploy the application
92
92
93
-
To deploy your application, use the [kubectl apply][kubectl-apply] command. This command parses the manifest file and creates the defined Kubernetes objects. Specify the sample manifest file, as shown in the following example:
93
+
To deploy your application, use the [`kubectl apply`][kubectl-apply] command, specifying the sample manifest file. This command parses the manifest file and creates the defined Kubernetes objects.
94
94
95
95
```console
96
96
kubectl apply -f azure-vote-all-in-one-redis.yaml
@@ -111,13 +111,13 @@ service "azure-vote-front" created
111
111
112
112
When the application runs, a Kubernetes service exposes the application front end to the internet. This process can take a few minutes to complete.
113
113
114
-
To monitor progress, use the [kubectl get service][kubectl-get] command with the `--watch` argument.
114
+
To monitor progress, use the [`kubectl get service`][kubectl-get] command with the `--watch` argument.
115
115
116
116
```console
117
117
kubectl get service azure-vote-front --watch
118
118
```
119
119
120
-
Initially the *EXTERNAL-IP* for the *azure-vote-front* service is shown as *pending*:
120
+
Initially the *EXTERNAL-IP* for the *azure-vote-front* service shows as *pending*.
To see the application in action, open a web browser to the external IP address of your service:
132
+
To see the application in action, open a web browser to the external IP address of your service.
133
133
134
134
:::image type="content" source="./media/container-service-kubernetes-tutorials/azure-vote.png" alt-text="Screenshot showing the container image Azure Voting App running in an AKS cluster opened in a local web browser" lightbox="./media/container-service-kubernetes-tutorials/azure-vote.png":::
135
135
136
-
If the application didn't load, it might be due to an authorization problem with your image registry. To view the status of your containers, use the `kubectl get pods` command. If the container images can't be pulled, see [Authenticate with Azure Container Registry from Azure Kubernetes Service](cluster-container-registry-integration.md).
136
+
If the application doesn't load, it might be an authorization problem with your image registry. To view the status of your containers, use the `kubectl get pods` command. If you can't pull the container images, see [Authenticate with Azure Container Registry from Azure Kubernetes Service](cluster-container-registry-integration.md).
137
137
138
138
## Next steps
139
139
140
-
In this tutorial, a sample Azure vote application was deployed to a Kubernetes cluster in AKS. You learned how to:
140
+
In this tutorial, you deployed a sample Azure vote application to a Kubernetes cluster in AKS. You learned how to:
141
141
142
142
> [!div class="checklist"]
143
-
> * Update a Kubernetes manifest files
144
-
> * Run an application in Kubernetes
145
-
> * Test the application
143
+
>
144
+
> * Update a Kubernetes manifest file.
145
+
> * Run an application in Kubernetes.
146
+
> * Test the application.
146
147
147
-
Advance to the next tutorial to learn how to scale a Kubernetes application and the underlying Kubernetes infrastructure.
148
+
In the next tutorial, you'll learn how to scale a Kubernetes application and the underlying Kubernetes infrastructure.
148
149
149
150
> [!div class="nextstepaction"]
150
151
> [Scale Kubernetes application and infrastructure][aks-tutorial-scale]
Copy file name to clipboardExpand all lines: articles/application-gateway/configuration-listeners.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,9 +85,9 @@ To configure a global custom error page, see [Azure PowerShell configuration](./
85
85
86
86
## TLS policy
87
87
88
-
You can centralize TLS/SSL certificate management and reduce encryption-decryption overhead for a backend server farm. Centralized TLS handling also lets you specify a central TLS policy that's suited to your security requirements. You can choose *default*, *predefined*, or *custom* TLS policy.
88
+
You can centralize TLS/SSL certificate management and reduce encryption-decryption overhead for a backend server farm. Centralized TLS handling also lets you specify a central TLS policy that's suited to your security requirements. You can choose *predefined* or *custom* TLS policy.
89
89
90
-
You configure TLS policy to control TLS protocol versions. You can configure an application gateway to use a minimum protocol version for TLS handshakes from TLS1.0, TLS1.1, and TLS1.2. By default, SSL 2.0 and 3.0 are disabled and aren't configurable. For more information, see [Application Gateway TLS policy overview](./application-gateway-ssl-policy-overview.md).
90
+
You configure TLS policy to control TLS protocol versions. You can configure an application gateway to use a minimum protocol version for TLS handshakes from TLS1.0, TLS1.1, TLS1.2, and TLS1.3. By default, SSL 2.0 and 3.0 are disabled and aren't configurable. For more information, see [Application Gateway TLS policy overview](./application-gateway-ssl-policy-overview.md).
91
91
92
92
After you create a listener, you associate it with a request-routing rule. That rule determines how requests that are received on the listener are routed to the back end.
Copy file name to clipboardExpand all lines: articles/application-gateway/ingress-controller-install-new.md
+8-3Lines changed: 8 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,9 +46,9 @@ Follow the steps below to create an Azure Active Directory (Azure AD) [service p
46
46
The `appId` and `password` values from the JSON output will be used in the following steps
47
47
48
48
49
-
1. Use the `appId` from the previous command's output to get the `objectId` of the new service principal:
49
+
1. Use the `appId` from the previous command's output to get the `id` of the new service principal:
50
50
```azurecli
51
-
objectId=$(az ad sp show --id $appId --query "objectId" -o tsv)
51
+
objectId=$(az ad sp show --id $appId --query "id" -o tsv)
52
52
```
53
53
The output of this command is `objectId`, which will be used in the Azure Resource Manager template below
54
54
@@ -250,8 +250,13 @@ Kubernetes. We'll use it to install the `application-gateway-kubernetes-ingress`
250
250
nano helm-config.yaml
251
251
```
252
252
253
+
> [!NOTE]
254
+
> **For deploying to Sovereign Clouds (e.g., Azure Government)**, the `appgw.environment` configuration parameter must be added and set to the appropriate value as documented below.
255
+
256
+
253
257
Values:
254
258
- `verbosityLevel`: Sets the verbosity level of the AGIC logging infrastructure. See [Logging Levels](https://github.com/Azure/application-gateway-kubernetes-ingress/blob/463a87213bbc3106af6fce0f4023477216d2ad78/docs/troubleshooting.md#logging-levels) for possible values.
Copy file name to clipboardExpand all lines: articles/automation/shared-resources/certificates.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Manage certificates in Azure Automation
3
3
description: This article tells how to work with certificates for access by runbooks and DSC configurations.
4
4
services: automation
5
5
ms.subservice: shared-capabilities
6
-
ms.date: 12/22/2020
6
+
ms.date: 01/04/2023
7
7
ms.topic: conceptual
8
8
ms.custom: devx-track-azurepowershell
9
9
---
@@ -59,7 +59,7 @@ When you create a new certificate, you upload a .cer or .pfx file to Automation.
59
59
1. From your Automation account, on the left-hand pane select **Certificates** under **Shared Resource**.
60
60
1. On the **Certificates** page, select **Add a certificate**.
61
61
1. In the **Name** field, type a name for the certificate.
62
-
1. To browse for a **.cer** or **.pfx** file, under **Upload a certificate file**, choose **Select a file**. If you select a **.pfx** file, specify a password and indicate if it can be exported.
62
+
1. To browse for a **.cer** or **.pfx** file, under **Upload a certificate file**, choose **Select a file**. If you select a **.pfx** file, specify a password and indicate if it can be exported. If you are using Azure Automation portal to upload certificates, it might fail for partner (CSP) accounts. We recommend that you use [PowerShell cmdlets](#powershell-cmdlets-to-access-certificates) as a workaround to overcome this issue.
63
63
1. Select **Create** to save the new certificate asset.
0 commit comments