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
PowerShell module to identify viral users in an Azure AD tenant and
44
+
reset user redemption status.
45
+
46
+
Once the above steps are complete, when users with unmanaged Azure AD accounts try to access your tenant, they'll re-redeem their invitations. However, because Email OTP is enabled, Azure AD will prevent users from redeeming with an existing unmanaged Azure AD account and they’ll redeem with another account type. Google Federation and SAML/WS-Fed aren't enabled by default. So by default, these users will redeem with either an MSA or Email OTP, with MSA taking precedence. For a full explanation on the B2B redemption precedence, refer to the [redemption precedence flow chart](https://docs.microsoft.com/azure/active-directory/external-identities/redemption-experience#invitation-redemption-flow).
47
+
48
+
## Overtaken tenants and domains
49
+
50
+
Some tenants created as unmanaged tenants can be taken over and
51
+
converted to a managed tenant. See, [take over an unmanaged directory as
52
+
administrator in Azure AD](https://docs.microsoft.com/azure/active-directory/enterprise-users/domains-admin-takeover).
53
+
54
+
In some cases, overtaken domains might not be updated, for example, missing a DNS TXT record and therefore become flagged as unmanaged. Implications are:
55
+
56
+
- For guest users who belong to formerly unmanaged tenants, redemption status is reset and one consent prompt appears. Redemption occurs with same account as before.
57
+
58
+
- After unmanaged user redemption status is reset, the tool might identify unmanaged users that are false positives.
59
+
60
+
## Reset redemption using a sample application
61
+
62
+
Before you begin, to identify and reset unmanaged Azure AD account redemption:
Copy file name to clipboardExpand all lines: articles/aks/learn/quick-kubernetes-deploy-cli.md
+20-16Lines changed: 20 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: 'Quickstart: Deploy an AKS cluster by using Azure CLI'
3
3
description: Learn how to quickly create a Kubernetes cluster, deploy an application, and monitor performance in Azure Kubernetes Service (AKS) using the Azure CLI.
#Customer intent: As a developer or cluster operator, I want to quickly create an AKS cluster and deploy an application so that I can see how to run and monitor applications using the managed Kubernetes service in Azure.
9
9
---
@@ -27,21 +27,21 @@ To learn more about creating a Windows Server node pool, see [Create an AKS clus
27
27
28
28
- This article requires version 2.0.64 or later of the Azure CLI. If using Azure Cloud Shell, the latest version is already installed.
29
29
30
-
- The identity you are using to create your cluster has the appropriate minimum permissions. For more details on access and identity for AKS, see [Access and identity options for Azure Kubernetes Service (AKS)](../concepts-identity.md).
30
+
- The identity you are using to create your cluster has the appropriate minimum permissions. For more details on access and identity for AKS, see [Access and identity options for Azure Kubernetes Service (AKS)][aks-identity-concepts].
31
31
32
32
- If you have multiple Azure subscriptions, select the appropriate subscription ID in which the resources should be billed using the
33
-
[az account](/cli/azure/account) command.
33
+
[az account][az-account] command.
34
34
35
-
- Verify *Microsoft.OperationsManagement* and *Microsoft.OperationalInsights* are registered on your subscription. To check the registration status:
35
+
- Verify *Microsoft.OperationsManagement* and *Microsoft.OperationalInsights*providers are registered on your subscription. These are Azure resource providers required to support [Container insights][azure-monitor-containers]. To check the registration status, run the following commands:
36
36
37
-
```azurecli-interactive
37
+
```azurecli
38
38
az provider show -n Microsoft.OperationsManagement -o table
39
39
az provider show -n Microsoft.OperationalInsights -o table
40
40
```
41
41
42
-
If they are not registered, register *Microsoft.OperationsManagement* and *Microsoft.OperationalInsights* using:
42
+
If they are not registered, register *Microsoft.OperationsManagement* and *Microsoft.OperationalInsights* using the following commands:
43
43
44
-
```azurecli-interactive
44
+
```azurecli
45
45
az provider register --namespace Microsoft.OperationsManagement
46
46
az provider register --namespace Microsoft.OperationalInsights
47
47
```
@@ -51,7 +51,7 @@ To learn more about creating a Windows Server node pool, see [Create an AKS clus
51
51
52
52
## Create a resource group
53
53
54
-
An [Azure resource group](../../azure-resource-manager/management/overview.md) is a logical group in which Azure resources are deployed and managed. When you create a resource group, you are prompted to specify a location. This location is:
54
+
An [Azure resource group][azure-resource-group] is a logical group in which Azure resources are deployed and managed. When you create a resource group, you are prompted to specify a location. This location is:
55
55
56
56
* The storage location of your resource group metadata.
57
57
* Where your resources will run in Azure if you don't specify another region during resource creation.
@@ -81,10 +81,10 @@ The following output example resembles successful creation of the resource group
81
81
82
82
## Create AKS cluster
83
83
84
-
Create an AKS cluster using the [az aks create][az-aks-create] command with the *--enable-addons monitoring* parameter to enable [Container insights][azure-monitor-containers]. The following example creates a cluster named *myAKSCluster* with one node:
84
+
Create an AKS cluster using the [az aks create][az-aks-create] command with the *--enable-addons monitoring* parameter to enable [Container insights][azure-monitor-containers]. The following example creates a cluster named *myAKSCluster* with one node and enables a system-assigned managed identity:
85
85
86
86
```azurecli-interactive
87
-
az aks create --resource-group myResourceGroup --name myAKSCluster --node-count 1 --enable-addons monitoring --generate-ssh-keys
87
+
az aks create -g myResourceGroup -n myManagedCluster --enable-managed-identity --node-count 1 --enable-addons monitoring
88
88
```
89
89
90
90
After a few minutes, the command completes and returns JSON-formatted information about the cluster.
@@ -102,9 +102,10 @@ To manage a Kubernetes cluster, use the Kubernetes command-line client, [kubectl
102
102
az aks install-cli
103
103
```
104
104
105
-
2. Configure `kubectl` to connect to your Kubernetes cluster using the [az aks get-credentials][az-aks-get-credentials] command. The following command:
106
-
* Downloads credentials and configures the Kubernetes CLI to use them.
107
-
* Uses `~/.kube/config`, the default location for the [Kubernetes configuration file][kubeconfig-file]. Specify a different location for your Kubernetes configuration file using *--file* argument.
105
+
2. Configure `kubectl` to connect to your Kubernetes cluster using the [az aks get-credentials][az-aks-get-credentials] command. The following command:
106
+
107
+
* Downloads credentials and configures the Kubernetes CLI to use them.
108
+
* Uses `~/.kube/config`, the default location for the [Kubernetes configuration file][kubeconfig-file]. Specify a different location for your Kubernetes configuration file using *--file* argument.
108
109
109
110
```azurecli-interactive
110
111
az aks get-credentials --resource-group myResourceGroup --name myAKSCluster
@@ -137,9 +138,9 @@ Two [Kubernetes Services][kubernetes-service] are also created:
137
138
* An internal service for the Redis instance.
138
139
* An external service to access the Azure Vote application from the internet.
139
140
140
-
1. Create a file named `azure-vote.yaml`.
141
-
* If you use the Azure Cloud Shell, this file can be created using `code`, `vi`, or `nano` as if working on a virtual or physical system
142
-
1. Copy in the following YAML definition:
141
+
1. Create a file named `azure-vote.yaml` and copy in the following manifest.
142
+
143
+
* If you use the Azure Cloud Shell, this file can be created using `code`, `vi`, or `nano` as if working on a virtual or physical system.
143
144
144
145
```yaml
145
146
apiVersion: apps/v1
@@ -303,7 +304,10 @@ This quickstart is for introductory purposes. For guidance on a creating full so
0 commit comments