Skip to content

Commit ed77706

Browse files
authored
Merge pull request #209311 from MicrosoftDocs/main
Publish to Live, Friday 4AM PST, 8/26
2 parents 887b715 + 7f33106 commit ed77706

File tree

130 files changed

+1350
-693
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

130 files changed

+1350
-693
lines changed

.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22348,6 +22348,11 @@
2234822348
"redirect_url": "/azure/storage/common/customer-managed-keys-configure-key-vault",
2234922349
"redirect_document_id": false
2235022350
},
22351+
{
22352+
"source_path_from_root": "/articles/storage/common/customer-managed-keys-configure-key-vault.md",
22353+
"redirect_url": "/azure/storage/common/customer-managed-keys-configure-existing-account",
22354+
"redirect_document_id": false
22355+
},
2235122356
{
2235222357
"source_path_from_root": "/articles/storage/common/encryption-customer-managed-keys.md",
2235322358
"redirect_url": "/azure/storage/common/customer-managed-keys-overview",

articles/active-directory-b2c/configure-authentication-sample-react-spa-app.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -171,7 +171,7 @@ In the sample folder, open the *config.json* file. This file contains informatio
171171

172172
|Section |Key |Value |
173173
|---------|---------|---------|
174-
|credentials|tenantName| The first part of your Azure AD B2C [tenant name](tenant-management.md#get-your-tenant-name). For example: `contoso`.|
174+
|credentials|tenantName| Your Azure AD B2C [domain/tenant name](tenant-management.md#get-your-tenant-name). For example: `contoso.ommicrosoft.com`.|
175175
|credentials|clientID| The web API application ID from step [2.1](#21-register-the-web-api-application). In the [earlier diagram](#app-registration), it's the application with **App ID: 2**.|
176176
|credentials| issuer| (Optional) The token issuer `iss` claim value. Azure AD B2C by default returns the token in the following format: `https://<your-tenant-name>.b2clogin.com/<your-tenant-ID>/v2.0/`. Replace `<your-tenant-name>` with the first part of your Azure AD B2C [tenant name](tenant-management.md#get-your-tenant-name). Replace `<your-tenant-ID>` with your [Azure AD B2C tenant ID](tenant-management.md#get-your-tenant-id). |
177177
|policies|policyName|The user flow or custom policy that you created in [step 1](#step-1-configure-your-user-flow). If your application uses multiple user flows or custom policies, specify only one. For example, use the sign-up or sign-in user flow.|
@@ -182,7 +182,7 @@ Your final configuration file should look like the following JSON:
182182
```json
183183
{
184184
"credentials": {
185-
"tenantName": "<your-tenant-name>",
185+
"tenantName": "<your-tenant-name>.ommicrosoft.com",
186186
"clientID": "<your-webapi-application-ID>",
187187
"issuer": "https://<your-tenant-name>.b2clogin.com/<your-tenant-ID>/v2.0/"
188188
},

articles/active-directory-b2c/microsoft-graph-operations.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -60,8 +60,8 @@ Note, the [list](/graph/api/authentication-list-phonemethods) operation returns
6060

6161
An email address that can be used by a [username sign-in account](sign-in-options.md#username-sign-in) to reset the password. For more information, see [Azure AD authentication methods API](/graph/api/resources/emailauthenticationmethod).
6262

63-
- [Add](/graph/api/emailauthenticationmethod-post)
64-
- [List](/graph/api/emailauthenticationmethod-list)
63+
- [Add](/graph/api/authentication-post-emailmethods)
64+
- [List](/graph/api/authentication-list-emailmethods)
6565
- [Get](/graph/api/emailauthenticationmethod-get)
6666
- [Update](/graph/api/emailauthenticationmethod-update)
6767
- [Delete](/graph/api/emailauthenticationmethod-delete)

articles/active-directory/app-provisioning/on-premises-scim-provisioning.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.service: active-directory
77
ms.subservice: app-provisioning
88
ms.topic: conceptual
99
ms.workload: identity
10-
ms.date: 07/05/2022
10+
ms.date: 08/25/2022
1111
ms.author: billmath
1212
ms.reviewer: arvinh
1313
---
@@ -22,6 +22,7 @@ The Azure Active Directory (Azure AD) provisioning service supports a [SCIM 2.0]
2222
- An Azure AD tenant with Azure AD Premium P1 or Premium P2 (or EMS E3 or E5). [!INCLUDE [active-directory-p1-license.md](../../../includes/active-directory-p1-license.md)]
2323
- Administrator role for installing the agent. This task is a one-time effort and should be an Azure account that's either a hybrid administrator or a global administrator.
2424
- Administrator role for configuring the application in the cloud (application administrator, cloud application administrator, global administrator, or a custom role with permissions).
25+
- A computer with at least 3 GB of RAM, to host a provisioning agent. The computer should have Windows Server 2016 or a later version of Windows Server, with connectivity to the target application, and with outbound connectivity to login.microsoftonline.com, other Microsoft Online Services and Azure domains. An example is a Windows Server 2016 virtual machine hosted in Azure IaaS or behind a proxy.
2526

2627
## Deploying Azure AD provisioning agent
2728
The Azure AD Provisioning agent can be deployed on the same server hosting a SCIM enabled application, or a seperate server, providing it has line of sight to the application's SCIM endpoint. A single agent also supports provision to multiple applications hosted locally on the same server or seperate hosts, again as long as each SCIM endpoint is reachable by the agent.
@@ -49,6 +50,9 @@ Once the agent is installed, no further configuration is necesary on-prem, and a
4950
12. Go to the **Provisioning** pane, and select **Start provisioning**.
5051
13. Monitor using the [provisioning logs](../../active-directory/reports-monitoring/concept-provisioning-logs.md).
5152

53+
The following video provides an overview of on-premises provisoning.
54+
> [!VIDEO https://www.youtube.com/embed/QdfdpaFolys]
55+
5256
## Additional requirements
5357
* Ensure your [SCIM](https://techcommunity.microsoft.com/t5/identity-standards-blog/provisioning-with-scim-getting-started/ba-p/880010) implementation meets the [Azure AD SCIM requirements](use-scim-to-provision-users-and-groups.md).
5458

articles/active-directory/verifiable-credentials/verifiable-credentials-configure-verifier.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -127,7 +127,7 @@ Now you are ready to present and verify your first verified credential expert ca
127127
1. From Visual Studio Code, run the *Verifiable_credentials_DotNet* project. Or from the command shell, run the following commands:
128128

129129
```bash
130-
cd active-directory-verifiable-credentials-dotnet/1. asp-net-core-api-idtokenhint
130+
cd active-directory-verifiable-credentials-dotnet/1-asp-net-core-api-idtokenhint
131131
dotnet build "asp-net-core-api-idtokenhint.csproj" -c Debug -o .\bin\Debug\netcoreapp3.1
132132
dotnet run
133133
```

articles/applied-ai-services/form-recognizer/includes/input-requirements.md

Lines changed: 21 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,19 +3,37 @@ author: laujan
33
ms.service: applied-ai-services
44
ms.subservice: forms-recognizer
55
ms.topic: include
6-
ms.date: 07/27/2022
6+
ms.date: 08/25/2022
77
ms.author: lajanuar
8-
ms.custom: ignite-fall-2021
98
---
109
<!-- markdownlint-disable MD041 -->
1110

1211
* For best results, provide one clear photo or high-quality scan per document.
13-
* Supported file formats: JPEG/JPG, PNG, BMP, TIFF, and PDF (text-embedded or scanned). Text-embedded PDFs are best to eliminate the possibility of error in character extraction and location. Additionally, only API version`2022/06/30` supports Microsoft Word (DOCX), Excel (XLS), PowerPoint (PPT), and HTML files in Read model.
12+
13+
* Supported file formats:
14+
15+
|Model | PDF |Image: </br>JPEG/JPG, PNG, BMP, and TIFF | Microsoft Office: </br> Word (DOCX), Excel (XLS), PowerPoint (PPT), and HTML|
16+
|--------|:----:|:-----:|:---------------:
17+
|Read | ✔ | ✔ | &#x2731; **REST API version**</br> **`2022/06/30-preview`**
18+
|Layout ||| |
19+
|General&nbsp;Document||| |
20+
|Prebuilt ||| |
21+
|Custom ||| |
22+
23+
&#x2731; Microsoft Office files are currently not supported for other models or versions.
24+
1425
* For PDF and TIFF, up to 2000 pages can be processed (with a free tier subscription, only the first two pages are processed).
26+
1527
* The file size for analyzing documents must be _less than_ 500 MB for paid (S0) tier and 4 MB for free (F0) tier.
28+
1629
* Image dimensions must be between 50 x 50 pixels and 10,000 px x 10,000 pixels.
30+
1731
* PDF dimensions are up to 17 x 17 inches, corresponding to Legal or A3 paper size, or smaller.
32+
1833
* If your PDFs are password-locked, you must remove the lock before submission.
34+
1935
* The minimum height of the text to be extracted is 12 pixels for a 1024 x 768 pixel image. This dimension corresponds to about 8-point text at 150 dots per inch (DPI).
36+
2037
* For custom model training, the maximum number of pages for training data is 500 for the custom template model and 50,000 for the custom neural model.
38+
2139
* For custom model training, the total size of training data is 50 MB for template model and 1G-MB for the neural model.

articles/applied-ai-services/form-recognizer/whats-new.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ Form Recognizer service is updated on an ongoing basis. Bookmark this page to st
2121

2222
### Form Recognizer v3.0 generally available
2323

24-
**Form Recognizer REST API v3.0 is now generally available and ready for use in production applications!**
24+
**Form Recognizer REST API v3.0 is now generally available and ready for use in production applications!** Update your applications with [**REST API version 2022-08-31**](https://westus.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-2022-08-31/operations/AnalyzeDocument).
2525

2626
#### The August release introduces the following new capabilities and updates:
2727

@@ -885,4 +885,4 @@ Complete a [quickstart](./quickstarts/try-sdk-rest-api.md) to get started writin
885885

886886
## See also
887887

888-
* [What is Form Recognizer?](./overview.md)
888+
* [What is Form Recognizer?](./overview.md)

articles/automanage/automanage-arc.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ Automanage supports the following operating systems for Azure Arc-enabled server
3232
|[Update Management](../automation/update-management/overview.md) |You can use Update Management in Azure Automation to manage operating system updates for your machines. You can quickly assess the status of available updates on all agent machines and manage the process of installing required updates for servers. |Production, Dev/Test |
3333
|[Microsoft Antimalware](../security/fundamentals/antimalware.md) |Microsoft Antimalware for Azure is a free real-time protection that helps identify and remove viruses, spyware, and other malicious software. It generates alerts when known malicious or unwanted software tries to install itself or run on your Azure systems. **Note:** Microsoft Antimalware requires that there be no other antimalware software installed, or it may fail to work. This is also only supported for Windows Server 2016 and above. |Production, Dev/Test |
3434
|[Change Tracking & Inventory](../automation/change-tracking/overview.md) |Change Tracking and Inventory combines change tracking and inventory functions to allow you to track virtual machine and server infrastructure changes. The service supports change tracking across services, daemons software, registry, and files in your environment to help you diagnose unwanted changes and raise alerts. Inventory support allows you to query in-guest resources for visibility into installed applications and other configuration items. |Production, Dev/Test |
35-
|[Azure Guest Configuration](../governance/machine-configuration/overview.md) | Guest Configuration policy is used to monitor the configuration and report on the compliance of the machine. The Automanage service will install the Azure security baseline using the Guest Configuration extension. For Arc machines, the guest configuration service will install the baseline in audit-only mode. You will be able to see where your VM is out of compliance with the baseline, but noncompliance won't be automatically remediated. |Production, Dev/Test |
35+
|[Machine Configuration](../governance/machine-configuration/overview.md) | Machine Configuration policy is used to monitor the configuration and report on the compliance of the machine. The Automanage service will install the Azure security baseline using the Guest Configuration extension. For Arc machines, the machine configuration service will install the baseline in audit-only mode. You will be able to see where your VM is out of compliance with the baseline, but noncompliance won't be automatically remediated. |Production, Dev/Test |
3636
|[Azure Automation Account](../automation/automation-create-standalone-account.md) |Azure Automation supports management throughout the lifecycle of your infrastructure and applications. |Production, Dev/Test |
3737
|[Log Analytics Workspace](../azure-monitor/logs/log-analytics-overview.md) |Azure Monitor stores log data in a Log Analytics workspace, which is an Azure resource and a container where data is collected, aggregated, and serves as an administrative boundary. |Production, Dev/Test |
3838

articles/automanage/automanage-linux.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ Automanage supports the following Linux distributions and versions:
3737
|[Microsoft Defender for Cloud](../security-center/security-center-introduction.md) |Microsoft Defender for Cloud is a unified infrastructure security management system that strengthens the security posture of your data centers, and provides advanced threat protection across your hybrid workloads in the cloud. Learn [more](../security-center/security-center-introduction.md). Automanage will configure the subscription where your VM resides to the free-tier offering of Microsoft Defender for Cloud (Enhanced security off). If your subscription is already onboarded to Microsoft Defender for Cloud, then Automanage will not reconfigure it. |Production, Dev/Test |
3838
|[Update Management](../automation/update-management/overview.md) |You can use Update Management in Azure Automation to manage operating system updates for your machines. You can quickly assess the status of available updates on all agent machines and manage the process of installing required updates for servers. Learn [more](../automation/update-management/overview.md). |Production, Dev/Test |
3939
|[Change Tracking & Inventory](../automation/change-tracking/overview.md) |Change Tracking and Inventory combines change tracking and inventory functions to allow you to track virtual machine and server infrastructure changes. The service supports change tracking across services, daemons software, registry, and files in your environment to help you diagnose unwanted changes and raise alerts. Inventory support allows you to query in-guest resources for visibility into installed applications and other configuration items. Learn [more](../automation/change-tracking/overview.md). |Production, Dev/Test |
40-
|[Guest configuration](../governance/machine-configuration/overview.md) | Guest configuration is used to monitor the configuration and report on the compliance of the machine. The Automanage service will install the Azure Linux baseline using the guest configuration extension. For Linux machines, the guest configuration service will install the baseline in audit-only mode. You will be able to see where your VM is out of compliance with the baseline, but noncompliance won't be automatically remediated. Learn [more](../governance/machine-configuration/overview.md). |Production, Dev/Test |
40+
|[Machine configuration](../governance/machine-configuration/overview.md) | Machine configuration is used to monitor the configuration and report on the compliance of the machine. The Automanage service will install the Azure Linux baseline using the guest configuration extension. For Linux machines, the machine configuration service will install the baseline in audit-only mode. You will be able to see where your VM is out of compliance with the baseline, but noncompliance won't be automatically remediated. Learn [more](../governance/machine-configuration/overview.md). |Production, Dev/Test |
4141
|[Boot Diagnostics](../virtual-machines/boot-diagnostics.md) | Boot diagnostics is a debugging feature for Azure virtual machines (VM) that allows diagnosis of VM boot failures. Boot diagnostics enables a user to observe the state of their VM as it is booting up by collecting serial log information and screenshots. This will only be enabled for machines that are using managed disks. |Production, Dev/Test |
4242
|[Azure Automation Account](../automation/automation-create-standalone-account.md) |Azure Automation supports management throughout the lifecycle of your infrastructure and applications. Learn [more](../automation/automation-intro.md). |Production, Dev/Test |
4343
|[Log Analytics Workspace](../azure-monitor/logs/log-analytics-workspace-overview.md) |Azure Monitor stores log data in a Log Analytics workspace, which is an Azure resource and a container where data is collected, aggregated, and serves as an administrative boundary. Learn [more](../azure-monitor/logs/workspace-design.md). |Production, Dev/Test |

0 commit comments

Comments
 (0)