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/governance/entitlement-management-access-package-first.md
+5-1
Original file line number
Diff line number
Diff line change
@@ -42,7 +42,9 @@ In this tutorial, you learn how to:
42
42
> * Demonstrate how an internal user can request the access package
43
43
> * Approve the access request
44
44
45
-
If you don't have an Azure AD Premium P2 or Enterprise Mobility + Security E5 license, create a free [Enterprise Mobility + Security E5 trial](https://signup.microsoft.com/Signup?OfferId=87dd2714-d452-48a0-a809-d2f58c4f68b7&ali=1).
45
+
For a step-by-step demonstration of the process of deploying Azure Active Directory entitlement management, including creating your first access package, view the following video:
@@ -51,6 +53,8 @@ To use Azure AD entitlement management (Preview), you must have one of the follo
51
53
- Azure AD Premium P2
52
54
- Enterprise Mobility + Security (EMS) E5 license
53
55
56
+
If you don't have an Azure AD Premium P2 or Enterprise Mobility + Security E5 license, create a free [Enterprise Mobility + Security E5 trial](https://signup.microsoft.com/Signup?OfferId=87dd2714-d452-48a0-a809-d2f58c4f68b7&ali=1).
57
+
54
58
## Step 1: Set up users and group
55
59
56
60
A resource directory has one or more resources to share. In this step, you create a group named **Engineering Group** in the Woodgrove Bank directory that is the target resource for entitlement management. You also set up an internal requestor.
Copy file name to clipboardExpand all lines: articles/active-directory/governance/entitlement-management-overview.md
+4
Original file line number
Diff line number
Diff line change
@@ -32,6 +32,10 @@ Employees in organizations need access to various groups, applications, and site
32
32
33
33
Azure Active Directory (Azure AD) entitlement management can help you manage access to groups, applications, and SharePoint Online sites for internal users and also users outside your organization.
34
34
35
+
This video provides an overview of entitlement management and its business value:
#Customer intent: As an administrator, I want view resources a user has access to and view request logs for auditing purposes.
22
22
23
23
---
24
+
24
25
# View reports and logs in Azure AD entitlement management (Preview)
25
26
26
27
> [!IMPORTANT]
27
28
> Azure Active Directory (Azure AD) entitlement management is currently in public preview.
28
29
> This preview version is provided without a service level agreement, and it's not recommended for production workloads. Certain features might not be supported or might have constrained capabilities.
29
30
> For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
30
31
32
+
The user assignments report and Azure Active Directory audit log provide additional details about the users in your directory. As an administrator, you can view resources a user has access to and view request logs for auditing purposes or to determine the status of a user’s request. This article describes how to use the user assignments report and Azure AD audit logs.
33
+
34
+
Watch the following video to learn how to use entitlement management to manage access for users in Azure Active Directory:
Copy file name to clipboardExpand all lines: articles/aks/operator-best-practices-cluster-security.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -184,7 +184,7 @@ az aks get-upgrades --resource-group myResourceGroup --name myAKSCluster
184
184
You can then upgrade your AKS cluster using the [az aks upgrade][az-aks-upgrade] command. The upgrade process safely cordons and drains one node at a time, schedules pods on remaining nodes, and then deploys a new node running the latest OS and Kubernetes versions.
185
185
186
186
```azurecli-interactive
187
-
az aks upgrade --resource-group myResourceGroup --name myAKSCluster --kubernetes-version 1.11.8
187
+
az aks upgrade --resource-group myResourceGroup --name myAKSCluster --kubernetes-version KUBERNETES_VERSION
188
188
```
189
189
190
190
For more information about upgrades in AKS, see [Supported Kubernetes versions in AKS][aks-supported-versions] and [Upgrade an AKS cluster][aks-upgrade].
When the *EXTERNAL-IP* address changes from *pending* to an actual public IP address, use `CTRL-C` to stop the `kubectl` watch process. The following example output shows a valid public IP address assigned to the service:
Copy file name to clipboardExpand all lines: articles/aks/tutorial-kubernetes-scale.md
+7-6
Original file line number
Diff line number
Diff line change
@@ -74,12 +74,13 @@ Kubernetes supports [horizontal pod autoscaling][kubernetes-hpa] to adjust the n
74
74
az aks show --resource-group myResourceGroup --name myAKSCluster --query kubernetesVersion
75
75
```
76
76
77
-
If your AKS cluster is less than *1.10*, install the Metrics Server, otherwise skip this step. To install, clone the `metrics-server` GitHub repo and install the example resource definitions. To view the contents of these YAML definitions, see [Metrics Server for Kuberenetes 1.8+][metrics-server-github].
> If your AKS cluster is less than *1.10*, the Metrics Server is not automatically installed. To install, clone the `metrics-server` GitHub repo and install the example resource definitions. To view the contents of these YAML definitions, see [Metrics Server for Kuberenetes 1.8+][metrics-server-github].
To use the autoscaler, all containers in your pods and your pods must have CPU requests and limits defined. In the `azure-vote-front` deployment, the front-end container already requests 0.25 CPU, with a limit of 0.5 CPU. These resource requests and limits are defined as shown in the following example snippet:
@@ -56,16 +56,16 @@ To minimize disruption to running applications, AKS nodes are carefully cordoned
56
56
1. When the new node is ready and joined to the cluster, the Kubernetes scheduler begins to run pods on it.
57
57
1. The old node is deleted, and the next node in the cluster begins the cordon and drain process.
58
58
59
-
Use the [az aks upgrade][] command to upgrade the AKS cluster. The following example upgrades the cluster to Kubernetes version *1.10.9*.
59
+
Use the [az aks upgrade][] command to upgrade the AKS cluster. The following example upgrades the cluster to Kubernetes version *1.14.5*.
60
60
61
61
> [!NOTE]
62
-
> You can only upgrade one minor version at a time. For example, you can upgrade from *1.9.11* to *1.10.9*, but cannot upgrade from *1.9.6* to *1.11.x* directly. To upgrade from *1.9.11* to *1.11.x*, first upgrade from *1.9.11* to *1.10.x*, then perform another upgrade from *1.10.x* to *1.11.x*.
62
+
> You can only upgrade one minor version at a time. For example, you can upgrade from *1.12.x* to *1.13.x*, but cannot upgrade from *1.12.8* to *1.14.x* directly. To upgrade from *1.12.x* to *1.14.x*, first upgrade from *1.12.x* to *1.13.x*, then perform another upgrade from *1.13.x* to *1.14.x*.
63
63
64
64
```azurecli
65
-
az aks upgrade --resource-group myResourceGroup --name myAKSCluster --kubernetes-version 1.10.9
65
+
az aks upgrade --resource-group myResourceGroup --name myAKSCluster --kubernetes-version 1.14.5
66
66
```
67
67
68
-
The following condensed example output shows the *kubernetesVersion* now reports *1.10.9*:
68
+
The following condensed example output shows the *kubernetesVersion* now reports *1.14.5*:
69
69
70
70
```json
71
71
{
@@ -83,7 +83,7 @@ The following condensed example output shows the *kubernetesVersion* now reports
Copy file name to clipboardExpand all lines: articles/aks/upgrade-cluster.md
+10-10
Original file line number
Diff line number
Diff line change
@@ -32,26 +32,26 @@ az aks get-upgrades --resource-group myResourceGroup --name myAKSCluster --outpu
32
32
```
33
33
34
34
> [!NOTE]
35
-
> When you upgrade an AKS cluster, Kubernetes minor versions cannot be skipped. For example, upgrades between *1.11.x* -> *1.12.x* or *1.12.x* -> *1.13.x* are allowed, however *1.11.x* -> *1.13.x* is not.
35
+
> When you upgrade an AKS cluster, Kubernetes minor versions cannot be skipped. For example, upgrades between *1.12.x* -> *1.13.x* or *1.13.x* -> *1.14.x* are allowed, however *1.12.x* -> *1.14.x* is not.
36
36
>
37
-
> To upgrade, from *1.11.x* -> *1.13.x*, first upgrade from *1.11.x* -> *1.12.x*, then upgrade from *1.12.x* -> *1.13.x*.
37
+
> To upgrade, from *1.12.x* -> *1.14.x*, first upgrade from *1.12.x* -> *1.13.x*, then upgrade from *1.13.x* -> *1.14.x*.
38
38
39
-
The following example output shows that the cluster can be upgraded to version *1.12.7* or *1.12.8*:
39
+
The following example output shows that the cluster can be upgraded to version *1.13.9*:
40
40
41
41
```console
42
-
Name ResourceGroup MasterVersion NodePoolVersion Upgrades
With a list of available versions for your AKS cluster, use the [az aks upgrade][az-aks-upgrade] command to upgrade. During the upgrade process, AKS adds a new node to the cluster that runs the specified Kubernetes version, then carefully [cordon and drains][kubernetes-drain] one of the old nodes to minimize disruption to running applications. When the new node is confirmed as running application pods, the old node is deleted. This process repeats until all nodes in the cluster have been upgraded.
50
50
51
-
The following example upgrades a cluster to version *1.12.8*:
51
+
The following example upgrades a cluster to version *1.13.9*:
52
52
53
53
```azurecli-interactive
54
-
az aks upgrade --resource-group myResourceGroup --name myAKSCluster --kubernetes-version 1.12.8
54
+
az aks upgrade --resource-group myResourceGroup --name myAKSCluster --kubernetes-version 1.13.9
55
55
```
56
56
57
57
It takes a few minutes to upgrade the cluster, depending on how many nodes you have.
@@ -62,12 +62,12 @@ To confirm that the upgrade was successful, use the [az aks show][az-aks-show] c
62
62
az aks show --resource-group myResourceGroup --name myAKSCluster --output table
63
63
```
64
64
65
-
The following example output shows that the cluster now runs *1.12.8*:
65
+
The following example output shows that the cluster now runs *1.13.9*:
66
66
67
67
```json
68
68
Name Location ResourceGroup KubernetesVersion ProvisioningState Fqdn
0 commit comments