Skip to content

Commit 5873882

Browse files
committed
2 parents 8c5fa78 + cd1fb93 commit 5873882

File tree

37 files changed

+174
-110
lines changed

37 files changed

+174
-110
lines changed

articles/active-directory/develop/howto-authenticate-service-principal-powershell.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.subservice: develop
1010
ms.custom: aaddev, devx-track-azurepowershell
1111
ms.topic: how-to
1212
ms.tgt_pltfrm: multiple
13-
ms.date: 10/11/2021
13+
ms.date: 11/09/2022
1414
ms.author: ryanwi
1515
ms.reviewer: tomfitz
1616
---

articles/active-directory/develop/registration-config-how-to.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.subservice: develop
1010
ms.custom: aaddev
1111
ms.workload: identity
1212
ms.topic: conceptual
13-
ms.date: 09/27/2021
13+
ms.date: 11/09/2022
1414
ms.author: ryanwi
1515
ROBOTS: NOINDEX
1616
---

articles/active-directory/develop/test-throttle-service-limits.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.service: active-directory
99
ms.subservice: develop
1010
ms.topic: conceptual
1111
ms.workload: identity
12-
ms.date: 09/17/2021
12+
ms.date: 11/09/2022
1313
ms.author: ryanwi
1414
ms.reviewer: arcrowe
1515
#Customer intent: As a developer, I want to understand the throttling and service limits I might hit so that I can test my app without interruption.
@@ -64,4 +64,4 @@ Throttling behavior can depend on the type and number of requests. For example,
6464
When you exceed a throttling limit, you receive the HTTP status code `429 Too many requests` and your request fails. The response includes a `Retry-After` header value, which specifies the number of seconds your application should wait (or sleep) before sending the next request. Retry the request. If you send a request before the retry value has elapsed, your request isn't processed and a new retry value is returned. If the request fails again with a 429 error code, you are still being throttled. Continue to use the recommended `Retry-After` delay and retry the request until it succeeds.
6565

6666
## Next steps
67-
Learn how to [setup a test environment](test-setup-environment.md).
67+
Learn how to [setup a test environment](test-setup-environment.md).

articles/active-directory/hybrid/reference-connect-version-history.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -77,6 +77,15 @@ If you want all the latest features and updates, check this page and install wha
7777

7878
To read more about auto-upgrade, see [Azure AD Connect: Automatic upgrade](how-to-connect-install-automatic-upgrade.md).
7979

80+
## 2.1.20.0
81+
82+
### Release status:
83+
11/9/2022: Released for download
84+
85+
### Bug fixes
86+
87+
- We fixed a bug where the new employeeLeaveDateTime attribute was not syncing correctly in version 2.1.19.0. Note that if the incorrect attribute was already used in a rule, then the rule must be updated with the new attribute and any objects in the AAD connector space that have the incorrect attribute must be removed with the "Remove-ADSyncCSObject" cmdlet, and then a full sync cycle must be run.
88+
8089
## 2.1.19.0
8190

8291
### Release status:

articles/aks/azure-disk-volume.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,12 @@ This article assumes that you have an existing AKS cluster with 1.21 or later ve
2424

2525
If you want to interact with Azure disks on an AKS cluster with 1.20 or previous version, see the [Kubernetes plugin for Azure disks][kubernetes-disks].
2626

27+
The Azure Disks CSI driver has a limit of 32 volumes per node. The volume count will change based on the size of the node/node pool. Run the following command to determine the number of volumes that can be allocated per node:
28+
29+
```console
30+
kubectl get CSINode <nodename> -o yaml
31+
```
32+
2733
## Storage class static provisioning
2834

2935
The following table describes the Storage Class parameters for the Azure disk CSI driver static provisioning:

articles/aks/azure-disks-dynamic-pv.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.date: 07/21/2022
1515
A persistent volume represents a piece of storage that has been provisioned for use with Kubernetes pods. A persistent volume can be used by one or many pods, and can be dynamically or statically provisioned. This article shows you how to dynamically create persistent volumes with Azure Disks for use by a single pod in an Azure Kubernetes Service (AKS) cluster.
1616

1717
> [!NOTE]
18-
> An Azure Disks can only be mounted with *Access mode* type *ReadWriteOnce*, which makes it available to one node in AKS. If you need to share a persistent volume across multiple nodes, use [Azure Files][azure-files-pvc].
18+
> An Azure disk can only be mounted with *Access mode* type *ReadWriteOnce*, which makes it available to one node in AKS. If you need to share a persistent volume across multiple nodes, use [Azure Files][azure-files-pvc].
1919
2020
For more information on Kubernetes volumes, see [Storage options for applications in AKS][concepts-storage].
2121

@@ -25,6 +25,12 @@ This article assumes that you have an existing AKS cluster with 1.21 or later ve
2525

2626
You also need the Azure CLI version 2.0.59 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].
2727

28+
The Azure Disks CSI driver has a limit of 32 volumes per node. The volume count will change based on the size of the node/node pool. Run the following command to determine the number of volumes that can be allocated per node:
29+
30+
```console
31+
kubectl get CSINode <nodename> -o yaml
32+
```
33+
2834
## Built-in storage classes
2935

3036
A storage class is used to define how a unit of storage is dynamically created with a persistent volume. For more information on Kubernetes storage classes, see [Kubernetes Storage Classes][kubernetes-storage-classes].

articles/aks/concepts-storage.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -33,6 +33,9 @@ Kubernetes typically treats individual pods as ephemeral, disposable resources.
3333

3434
Traditional volumes are created as Kubernetes resources backed by Azure Storage. You can manually create data volumes to be assigned to pods directly, or have Kubernetes automatically create them. Data volumes can use: [Azure Disks][disks-types], [Azure Files][storage-files-planning], [Azure NetApp Files][azure-netapp-files-service-levels], or [Azure Blobs][storage-account-overview].
3535

36+
> [!NOTE]
37+
> The Azure Disks CSI driver has a limit of 32 volumes per node. Other Azure Storage services don't have an equivalent limit.
38+
3639
### Azure Disks
3740

3841
Use *Azure Disks* to create a Kubernetes *DataDisk* resource. Disks types include:
@@ -43,13 +46,13 @@ Use *Azure Disks* to create a Kubernetes *DataDisk* resource. Disks types includ
4346
* Standard HDDs
4447

4548
> [!TIP]
46-
>For most production and development workloads, use Premium SSD.
49+
> For most production and development workloads, use Premium SSD.
4750
48-
Since Azure Disks are mounted as *ReadWriteOnce*, they're only available to a single node. For storage volumes that can be accessed by pods on multiple nodes simultaneously, use Azure Files.
51+
Because Azure Disks are mounted as *ReadWriteOnce*, they're only available to a single node. For storage volumes that can be accessed by pods on multiple nodes simultaneously, use Azure Files.
4952

5053
### Azure Files
5154

52-
Use *Azure Files* to mount a Server Message Block (SMB) version 3.1.1 share or Network File System (NFS) version 4.1 share backed by an Azure storage accounts to pods. Files let you share data across multiple nodes and pods and can use:
55+
Use [Azure Files][azure-files-volume] to mount a Server Message Block (SMB) version 3.1.1 share or Network File System (NFS) version 4.1 share backed by an Azure storage account to pods. Azure Files let you share data across multiple nodes and pods and can use:
5356

5457
* Azure Premium storage backed by high-performance SSDs
5558
* Azure Standard storage backed by regular HDDs

articles/azure-monitor/change/change-analysis-troubleshoot.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -97,7 +97,9 @@ When filtering down to a particular resource in the Change Analysis standalone p
9797
1. In the Azure portal, select **All resources**.
9898
1. Select the actual resource you want to view.
9999
1. In that resource's left side menu, select **Diagnose and solve problems**.
100-
1. Select **Change details**.
100+
1. In the Change Analysis card, select **View change details**.
101+
102+
:::image type="content" source="./media/change-analysis/change-details-card.png" alt-text="Screenshot of viewing change details from the Change Analysis card in Diagnose and solve problems tool.":::
101103
102104
From here, you'll be able to view all of the changes for that one resource.
103105
18.1 KB
Loading

articles/azure-video-indexer/video-indexer-overview.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -23,14 +23,6 @@ Azure Video Indexer analyzes the video and audio content by running 30+ AI model
2323
2424
To start extracting insights with Azure Video Indexer, see the [how can I get started](#how-can-i-get-started-with-azure-video-indexer) section below.
2525

26-
## Compliance, Privacy and Security
27-
28-
As an important reminder, you must comply with all applicable laws in your use of Azure Video Indexer, and you may not use Azure Video Indexer or any Azure service in a manner that violates the rights of others, or that may be harmful to others.
29-
30-
Before uploading any video/image to Azure Video Indexer, You must have all the proper rights to use the video/image, including, where required by law, all the necessary consents from individuals (if any) in the video/image, for the use, processing, and storage of their data in Azure Video Indexer and Azure. Some jurisdictions may impose special legal requirements for the collection, online processing and storage of certain categories of data, such as biometric data. Before using Azure Video Indexer and Azure for the processing and storage of any data subject to special legal requirements, You must ensure compliance with any such legal requirements that may apply to You.
31-
32-
To learn about compliance, privacy and security in Azure Video Indexer please visit the Microsoft [Trust Center](https://www.microsoft.com/TrustCenter/CloudServices/Azure/default.aspx). For Microsoft's privacy obligations, data handling and retention practices, including how to delete your data, please review Microsoft's [Privacy Statement](https://privacy.microsoft.com/PrivacyStatement), the [Online Services Terms](https://www.microsoft.com/licensing/product-licensing/products?rtc=1) ("OST") and [Data Processing Addendum](https://www.microsoftvolumelicensing.com/DocumentSearch.aspx?Mode=3&DocumentTypeId=67) ("DPA"). By using Azure Video Indexer, you agree to be bound by the OST, DPA and the Privacy Statement.
33-
3426
## What can I do with Azure Video Indexer?
3527

3628
Azure Video Indexer's insights can be applied to many scenarios, among them are:
@@ -113,6 +105,14 @@ Learn how to [get started with Azure Video Indexer](video-indexer-get-started.md
113105

114106
Once you set up, start using [insights](video-indexer-output-json-v2.md) and check out other **How to guides**.
115107

108+
## Compliance, Privacy and Security
109+
110+
As an important reminder, you must comply with all applicable laws in your use of Azure Video Indexer, and you may not use Azure Video Indexer or any Azure service in a manner that violates the rights of others, or that may be harmful to others.
111+
112+
Before uploading any video/image to Azure Video Indexer, You must have all the proper rights to use the video/image, including, where required by law, all the necessary consents from individuals (if any) in the video/image, for the use, processing, and storage of their data in Azure Video Indexer and Azure. Some jurisdictions may impose special legal requirements for the collection, online processing and storage of certain categories of data, such as biometric data. Before using Azure Video Indexer and Azure for the processing and storage of any data subject to special legal requirements, You must ensure compliance with any such legal requirements that may apply to You.
113+
114+
To learn about compliance, privacy and security in Azure Video Indexer please visit the Microsoft [Trust Center](https://www.microsoft.com/TrustCenter/CloudServices/Azure/default.aspx). For Microsoft's privacy obligations, data handling and retention practices, including how to delete your data, please review Microsoft's [Privacy Statement](https://privacy.microsoft.com/PrivacyStatement), the [Online Services Terms](https://www.microsoft.com/licensing/product-licensing/products?rtc=1) ("OST") and [Data Processing Addendum](https://www.microsoftvolumelicensing.com/DocumentSearch.aspx?Mode=3&DocumentTypeId=67) ("DPA"). By using Azure Video Indexer, you agree to be bound by the OST, DPA and the Privacy Statement.
115+
116116
## Next steps
117117

118118
You're ready to get started with Azure Video Indexer. For more information, see the following articles:

0 commit comments

Comments
 (0)