Skip to content

Commit 56b5141

Browse files
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into 1678688-adding-zone-pivots-bing-video-search
2 parents 574d327 + 24c301c commit 56b5141

31 files changed

+773
-325
lines changed

articles/active-directory/conditional-access/concept-conditional-access-grant.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -78,6 +78,7 @@ This setting applies to the following iOS and Android apps:
7878
- Microsoft Kaizala
7979
- Microsoft Launcher
8080
- Microsoft Office
81+
- Microsoft Office Hub
8182
- Microsoft OneDrive
8283
- Microsoft OneNote
8384
- Microsoft Outlook

articles/aks/TOC.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -200,7 +200,7 @@
200200
items:
201201
- name: Create service principal
202202
href: kubernetes-service-principal.md
203-
- name: Use managed identities (preview)
203+
- name: Use managed identities
204204
href: use-managed-identity.md
205205
- name: Limit access to cluster configuration file
206206
href: control-kubeconfig-access.md

articles/aks/azure-disk-volume.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ You also need the Azure CLI version 2.0.59 or later installed and configured. Ru
2626

2727
## Create an Azure disk
2828

29-
When you create an Azure disk for use with AKS, you can create the disk resource in the **node** resource group. This approach allows the AKS cluster to access and manage the disk resource. If you instead create the disk in a separate resource group, you must grant the Azure Kubernetes Service (AKS) service principal for your cluster the `Contributor` role to the disk's resource group.
29+
When you create an Azure disk for use with AKS, you can create the disk resource in the **node** resource group. This approach allows the AKS cluster to access and manage the disk resource. If you instead create the disk in a separate resource group, you must grant the Azure Kubernetes Service (AKS) service principal for your cluster the `Contributor` role to the disk's resource group. Alternatively, you can use the system assigned managed identity for permissions instead of the service principal. For more information, see [Use managed identities](use-managed-identity.md).
3030

3131
For this article, create the disk in the node resource group. First, get the resource group name with the [az aks show][az-aks-show] command and add the `--query nodeResourceGroup` query parameter. The following example gets the node resource group for the AKS cluster name *myAKSCluster* in the resource group name *myResourceGroup*:
3232

articles/aks/configure-azure-cni.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,7 @@ This article shows you how to use *Azure CNI* networking to create and use a vir
2222
* The service principal used by the AKS cluster must have at least [Network Contributor](../role-based-access-control/built-in-roles.md#network-contributor) permissions on the subnet within your virtual network. If you wish to define a [custom role](../role-based-access-control/custom-roles.md) instead of using the built-in Network Contributor role, the following permissions are required:
2323
* `Microsoft.Network/virtualNetworks/subnets/join/action`
2424
* `Microsoft.Network/virtualNetworks/subnets/read`
25+
* Instead of a service principal, you can use the system assigned managed identity for permissions. For more information, see [Use managed identities](use-managed-identity.md).
2526

2627
## Plan IP addressing for your cluster
2728

articles/aks/static-ip.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -69,6 +69,8 @@ az role assignment create \
6969
--scope /subscriptions/<subscription id>/resourceGroups/<resource group name>
7070
```
7171

72+
Alternatively, you can use the system assigned managed identity for permissions instead of the service principal. For more information, see [Use managed identities](use-managed-identity.md).
73+
7274
To create a *LoadBalancer* service with the static public IP address, add the `loadBalancerIP` property and the value of the static public IP address to the YAML manifest. Create a file named `load-balancer-service.yaml` and copy in the following YAML. Provide your own public IP address created in the previous step. The following example also sets the annotation to the resource group named *myResourceGroup*. Provide your own resource group name.
7375

7476
```yaml

articles/aks/use-managed-identity.md

Lines changed: 14 additions & 38 deletions
Original file line numberDiff line numberDiff line change
@@ -5,11 +5,11 @@ services: container-service
55
author: saudas
66
manager: saudas
77
ms.topic: article
8-
ms.date: 09/11/2019
8+
ms.date: 03/10/2019
99
ms.author: saudas
1010
---
1111

12-
# Preview - Use managed identities in Azure Kubernetes Service
12+
# Use managed identities in Azure Kubernetes Service
1313

1414
Currently, an Azure Kubernetes Service (AKS) cluster (specifically, the Kubernetes cloud provider) requires a *service principal* to create additional resources like load balancers and managed disks in Azure. Either you must provide a service principal or AKS creates one on your behalf. Service principals typically have an expiration date. Clusters eventually reach a state in which the service principal must be renewed to keep the cluster working. Managing service principals adds complexity.
1515

@@ -20,46 +20,13 @@ AKS creates two managed identities:
2020
- **System-assigned managed identity**: The identity that the Kubernetes cloud provider uses to create Azure resources on behalf of the user. The life cycle of the system-assigned identity is tied to that of the cluster. The identity is deleted when the cluster is deleted.
2121
- **User-assigned managed identity**: The identity that's used for authorization in the cluster. For example, the user-assigned identity is used to authorize AKS to use access control records (ACRs), or to authorize the kubelet to get metadata from Azure.
2222

23-
In this preview period, a service principal is still required. It's used for authorization of add-ons such as monitoring, virtual nodes, Azure Policy, and HTTP application routing. Work is underway to remove the dependency of add-ons on the service principal name (SPN). Eventually, the requirement of an SPN in AKS will be removed completely.
24-
25-
> [!IMPORTANT]
26-
> AKS preview features are available on a self-service, opt-in basis. Previews are provided "as-is" and "as available," and are excluded from the Service Level Agreements and limited warranty. AKS previews are partially covered by customer support on best-effort basis. As such, these features are not meant for production use. For more information, see the following support articles:
27-
>
28-
> - [AKS Support Policies](support-policies.md)
29-
> - [Azure Support FAQ](faq.md)
23+
Add-ons also authenticate using a managed identity. For each add-on, a managed identity is created by AKS and lasts for the life of the add-on. For creating and using your own VNet, static IP address, or attached Azure disk where the resources are outside of the MC_* resource group, use the PrincipalID of the cluster to perform a role assignment. For more information on role assignment, see [Delegate access to other Azure resources](kubernetes-service-principal.md#delegate-access-to-other-azure-resources).
3024

3125
## Before you begin
3226

33-
You must have the following resources installed:
34-
35-
- The Azure CLI, version 2.0.70 or later
36-
- The aks-preview 0.4.14 extension
37-
38-
To install the aks-preview 0.4.14 extension or later, use the following Azure CLI commands:
39-
40-
```azurecli
41-
az extension add --name aks-preview
42-
az extension list
43-
```
44-
45-
> [!CAUTION]
46-
> After you register a feature on a subscription, you can't currently unregister that feature. When you enable some preview features, defaults might be used for all AKS clusters created afterward in the subscription. Don't enable preview features on production subscriptions. Instead, use a separate subscription to test preview features and gather feedback.
47-
48-
```azurecli-interactive
49-
az feature register --name MSIPreview --namespace Microsoft.ContainerService
50-
```
27+
You must have the following resource installed:
5128

52-
It might take several minutes for the status to show as **Registered**. You can check the registration status by using the [az feature list](https://docs.microsoft.com/cli/azure/feature?view=azure-cli-latest#az-feature-list) command:
53-
54-
```azurecli-interactive
55-
az feature list -o table --query "[?contains(name, 'Microsoft.ContainerService/MSIPreview')].{Name:name,State:properties.state}"
56-
```
57-
58-
When the status shows as registered, refresh the registration of the `Microsoft.ContainerService` resource provider by using the [az provider register](https://docs.microsoft.com/cli/azure/provider?view=azure-cli-latest#az-provider-register) command:
59-
60-
```azurecli-interactive
61-
az provider register --namespace Microsoft.ContainerService
62-
```
29+
- The Azure CLI, version 2.2.0 or later
6330

6431
## Create an AKS cluster with managed identities
6532

@@ -78,6 +45,15 @@ Then, create an AKS cluster:
7845
az aks create -g MyResourceGroup -n MyManagedCluster --enable-managed-identity
7946
```
8047

48+
A successful cluster creation using managed identities contains this service principal profile information:
49+
50+
```json
51+
"servicePrincipalProfile": {
52+
"clientId": "msi",
53+
"secret": null
54+
}
55+
```
56+
8157
Finally, get credentials to access the cluster:
8258

8359
```azurecli-interactive

articles/aks/use-multiple-node-pools.md

Lines changed: 1 addition & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This article shows you how to create and manage multiple node pools in an AKS cl
1818

1919
## Before you begin
2020

21-
You need the Azure CLI version 2.0.76 or later installed and configured. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI][install-azure-cli].
21+
You need the Azure CLI version 2.2.0 or later installed and configured. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI][install-azure-cli].
2222

2323
## Limitations
2424

@@ -497,17 +497,6 @@ $ az aks nodepool list -g myResourceGroup --cluster-name myAKSCluster
497497

498498
The taint information is visible in Kubernetes for handling scheduling rules for nodes.
499499

500-
> [!IMPORTANT]
501-
> To use node pool labels and tags, you need the *aks-preview* CLI extension version 0.4.35 or higher. Install the *aks-preview* Azure CLI extension using the [az extension add][az-extension-add] command, then check for any available updates using the [az extension update][az-extension-update] command:
502-
>
503-
> ```azurecli-interactive
504-
> # Install the aks-preview extension
505-
> az extension add --name aks-preview
506-
>
507-
> # Update the extension to make sure you have the latest version installed
508-
> az extension update --name aks-preview
509-
> ```
510-
511500
You can also add labels to a node pool during node pool creation. Labels set at the node pool are added to each node in the node pool. These [labels are visible in Kubernetes][kubernetes-labels] for handling scheduling rules for nodes.
512501

513502
To create a node pool with a label, use [az aks nodepool add][az-aks-nodepool-add]. Specify the name *labelnp* and use the `--labels` parameter to specify *dept=IT* and *costcenter=9999* for labels.

articles/azure-resource-manager/management/azure-subscription-service-limits.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,8 @@
11
---
22
title: Azure subscription limits and quotas
33
description: Provides a list of common Azure subscription and service limits, quotas, and constraints. This article includes information on how to increase limits along with maximum values.
4-
5-
64
ms.topic: conceptual
7-
ms.date: 02/24/2020
5+
ms.date: 03/20/2020
86
---
97

108
# Azure subscription and service limits, quotas, and constraints

articles/cosmos-db/TOC.yml

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@
2929
href: create-sql-api-xamarin-dotnet.md
3030
- name: Tutorials
3131
items:
32-
- name: 1 - Create & manage data
32+
- name: 1 - Create and manage data
3333
items:
3434
- name: Build a console app
3535
items:
@@ -53,7 +53,7 @@
5353
href: mobile-apps-with-xamarin.md
5454
- name: 2 - Migrate data
5555
items:
56-
- name: Using Data migration tool
56+
- name: Using the Data Migration tool
5757
href: import-data.md
5858
- name: Using .NET bulk support
5959
href: tutorial-sql-api-dotnet-bulk-import.md
@@ -85,11 +85,11 @@
8585
href: resource-manager-samples.md
8686
- name: Concepts
8787
items:
88-
- name: NoSQL Vs relational databases
88+
- name: NoSQL vs. relational databases
8989
href: relational-nosql.md
9090
- name: Global distribution
9191
items:
92-
- name: Global distribution Overview
92+
- name: Global distribution overview
9393
displayName: replication, replicate, geo distribution
9494
href: distribute-data-globally.md
9595
- name: Consistency levels
@@ -582,7 +582,7 @@
582582
href: create-cassandra-python.md
583583
- name: Tutorials
584584
items:
585-
- name: 1 - Create & manage data
585+
- name: 1 - Create and manage data
586586
href: create-cassandra-api-account-java.md
587587
- name: 2 - Load data
588588
href: cassandra-api-load-data.md
@@ -601,15 +601,15 @@
601601
href: cassandra-change-feed.md
602602
- name: Store and manage Spring Data
603603
href: https://docs.microsoft.com/azure/java/spring-framework/configure-spring-data-apache-cassandra-with-cosmos-db?context=/azure/cosmos-db/context/context
604-
- name: Cassandra & Spark
604+
- name: Cassandra and Spark
605605
items:
606606
- name: Introduction
607607
href: cassandra-spark-generic.md
608608
- name: Connect using Databricks
609609
href: cassandra-spark-databricks.md
610610
- name: Connect using HDInsight
611611
href: cassandra-spark-hdinsight.md
612-
- name: Create keyspace & table
612+
- name: Create keyspace and table
613613
href: cassandra-spark-ddl-ops.md
614614
- name: Insert data
615615
href: cassandra-spark-create-ops.md
@@ -656,7 +656,7 @@
656656
href: create-mongodb-golang.md
657657
- name: Tutorials
658658
items:
659-
- name: 1 - Create & manage data
659+
- name: 1 - Create and manage data
660660
items:
661661
- name: Node.js console app
662662
href: mongodb-samples.md
@@ -802,7 +802,7 @@
802802
href: create-table-python.md
803803
- name: Tutorials
804804
items:
805-
- name: 1 - Create & manage data
805+
- name: 1 - Create and manage data
806806
href: tutorial-develop-table-dotnet.md
807807
- name: 2 - Migrate data
808808
displayName: import
@@ -989,11 +989,11 @@
989989
href: use-notebook-features-and-commands.md
990990
- name : Server-side programming
991991
items:
992-
- name: Write stored procedures, triggers, & UDFs
992+
- name: Write stored procedures, triggers, and UDFs
993993
href: how-to-write-stored-procedures-triggers-udfs.md
994-
- name: Write stored procedures & triggers with JavaScript query API
994+
- name: Write stored procedures and triggers with JavaScript query API
995995
href: how-to-write-javascript-query-api.md
996-
- name: Use stored procedures, triggers, & UDFs
996+
- name: Use stored procedures, triggers, and UDFs
997997
href: how-to-use-stored-procedures-triggers-udfs.md
998998
- name: Security
999999
items:

articles/cosmos-db/stored-procedures-triggers-udfs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ In Azure Cosmos DB, JavaScript runtime is hosted inside the database engine. Hen
5151

5252
### Scope of a transaction
5353

54-
If a stored procedure is associated with an Azure Cosmos container, then the stored procedure is executed in the transaction scope of a logical partition key. Each stored procedure execution must include a logical partition key value that corresponds to the scope of the transaction. For more information, see [Azure Cosmos DB partitioning](partition-data.md) article.
54+
Stored procedures are associated with an Azure Cosmos container and stored procedure execution is scoped to a logical partition key. Stored procedures must include a logical partition key value during execution that defines the logical partition for the scope of the transaction. For more information, see [Azure Cosmos DB partitioning](partition-data.md) article.
5555

5656
### Commit and rollback
5757

0 commit comments

Comments
 (0)