Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into deid-bicep

merged main

Author: josiahvinson

articles/api-center/enable-managed-api-analysis-linting.md

@@ -3,7 +3,7 @@ title: Managed API linting and analysis - Azure API Center
 description: Enable managed linting of API definitions in your API center to analyze compliance of APIs with the organization's API style guide.
 ms.service: azure-api-center
 ms.topic: how-to
-ms.date: 08/23/2024
+ms.date: 11/01/2024
 ms.author: danlep
 author: dlepow
 ms.custom: 
@@ -30,9 +30,7 @@ In this scenario:
 * Currently, only OpenAPI specification documents in JSON or YAML format are analyzed.
 * By default, you enable analysis with the [`spectral:oas` ruleset](https://docs.stoplight.io/docs/spectral/4dec24461f3af-open-api-rules). To learn more about the built-in rules, see the [Spectral GitHub repo](https://github.com/stoplightio/spectral/blob/develop/docs/reference/openapi-rules.md). 
 * Currently, you configure a single ruleset, and it's applied to all OpenAPI definitions in your API center.
-* The following are limits for maximum number of API definitions linted per 4 hours:
-    * Free tier: 10
-    * Standard tier: 100
+* There are [limits](../azure-resource-manager/management/azure-subscription-service-limits.md?toc=/azure/api-center/toc.json&bc=/azure/api-center/breadcrumb/toc.json#api-center-limits) for the maximum number of API definitions analyzed. Analysis can take a few minutes to up to 24 hours to complete.
 
 ## Prerequisites
 

articles/api-center/includes/api-center-service-limits.md

@@ -7,7 +7,7 @@ author: dlepow
 
 ms.service: azure-api-center
 ms.topic: include
-ms.date: 10/18/2024
+ms.date: 11/07/2024
 ms.author: danlep
 ms.custom: Include file
 ---
@@ -20,14 +20,16 @@ ms.custom: Include file
 | Maximum number of deployments per API | 10 | 10 |
 | Maximum number of environments | 20 | 20 |
 | Maximum number of workspaces  | 1 (Default) | 1 (Default) |
-| Maximum number of custom metadata properties per entity<sup>4</sup> | 10 | 20 |
+| Maximum number of custom metadata properties per entity<sup>3</sup> | 10 | 20 |
 | Maximum number of child properties in custom metadata property of type "object" | 10 |10 | 
 | Maximum requests per minute (data plane) | 3,000 | 6,000  |
-| Maximum number of API definitions [linted](../enable-managed-api-analysis-linting.md) per 4 hours | 10 | 100  |
+| Maximum number of APIs accessed through data plane API | 5 | 10,000 |
+| Maximum number of API definitions [analyzed](../enable-managed-api-analysis-linting.md) | 10 | 2,000<sup>4</sup>  |
 | Maximum number of linked API sources<sup>5</sup> | 1  |  3 |
+| Maximum number of APIs synchronized from a linked API source | 200 | 2,000<sup>4</sup>  |
 
-<sup>1</sup> Free plan provided for 90 days, then service is soft-deleted.<br/>
+<sup>1</sup> Free plan provided for 90 days, then service is soft-deleted. Use of full service features including API analysis and access through the data plane API is limited.<br/>
 <sup>2</sup> To increase a limit in the Standard plan, contact [support](https://azure.microsoft.com/support/options/).<br/>
-<sup>3</sup> In the Free plan, use of full service features including API analysis and access through the data plane API is limited to 5 APIs.<br/>
-<sup>4</sup> Custom metadata properties assigned to APIs, deployments, and environments.<br/>
-<sup>5</sup> Sources such as linked API Management instances. In the Free plan, synchronization from a linked API source is limited to 200 APIs and 5 API definitions.
+<sup>3</sup> Custom metadata properties assigned to APIs, deployments, and environments.<br/>
+<sup>4</sup> Process can take a few minutes to up to 24 hours to complete.<br/> 
+<sup>5</sup> Sources such as linked API Management instances. 

articles/api-center/synchronize-api-management-apis.md

@@ -27,8 +27,8 @@ When you link an API Management instance as an API source, the following happens
 API Management APIs automatically synchronize to the API center whenever existing APIs' settings change (for example, new versions are added), new APIs are created, or APIs are deleted. This synchronization is one-way from API Management to your Azure API center, meaning API updates in the API center aren't synchronized back to the API Management instance.
 
 > [!NOTE]
-> * API updates in API Management can take a few minutes to synchronize to your API center.
 > * There are [limits](../azure-resource-manager/management/azure-subscription-service-limits.md?toc=/azure/api-center/toc.json&bc=/azure/api-center/breadcrumb/toc.json#api-center-limits) for the number of linked API Management instances (API sources).
+> * API updates in API Management can take a few minutes to up to 24 hours to synchronize to your API center.
 
 ### Entities synchronized from API Management
 

articles/iot-edge/tutorial-configure-est-server.md

@@ -3,7 +3,7 @@ title: Tutorial - Configure Enrollment over Secure Transport Server (EST) for Az
 description: This tutorial shows you how to set up an Enrollment over Secure Transport (EST) server for Azure IoT Edge.
 author: PatAltimore
 ms.author: patricka
-ms.date: 06/10/2024
+ms.date: 11/07/2024
 ms.topic: tutorial
 ms.service: azure-iot-edge
 services: iot-edge
@@ -335,5 +335,5 @@ You can keep the resources and configurations that you created in this tutorial
 * To use EST server to issue Edge CA certificates, see [example configuration](https://github.com/Azure/iotedge/blob/main/edgelet/doc/est.md#edge-ca-certificate).
 * Using username and password to bootstrap authentication to EST server isn't recommended for production. Instead, consider using long-lived *bootstrap certificates* that can be stored onto the device during manufacturing [similar to the recommended approach for DPS](../iot-hub/iot-hub-x509ca-concept.md). To see how to configure bootstrap certificate for EST server, see [Authenticate a Device Using Certificates Issued Dynamically via EST](https://github.com/Azure/iotedge/blob/main/edgelet/doc/est.md).
 * EST server can be used to issue certificates for all devices in a hierarchy as well. Depending on if you have ISA-95 requirements, it may be necessary to run a chain of EST servers with one at every layer or use the API proxy module to forward the requests. To learn more, see [Kevin's blog](https://kevinsaye.wordpress.com/2021/07/21/deep-dive-creating-hierarchies-of-azure-iot-edge-devices-isa-95-part-3/).
-* For enterprise grade solutions, consider: [GlobalSign IoT Edge Enroll](https://www.globalsign.com/en/iot-edge-enroll) or [DigiCert IoT Device Manager](https://www.digicert.com/iot/iot-device-manager)
+* For enterprise grade solutions, consider: [GlobalSign IoT Edge Enroll](https://www.globalsign.com/en/iot-edge-enroll), [DigiCert IoT Device Manager](https://www.digicert.com/iot/iot-device-manager), and [Keytos EZCA](https://www.keytos.io/docs/azure-pki/azure-iot-hub/how-to-create-azure-iot-est-certificate-authority/).
 * To learn more about certificates, see [Understand how Azure IoT Edge uses certificates](iot-edge-certs.md).