Merge pull request #285679 from MicrosoftDocs/main

8/28 11:00 AM IST Publish

Author: PhilKang0704

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

@@ -14,8 +14,9 @@ ms.custom:
 
 This article explains how to enable API analysis in [Azure API Center](overview.md) without having to manage it yourself (preview). API analysis offers linting capabilities to analyze API definitions in your organization's API center. Linting ensures your API definitions adhere to organizational style rules, generating both individual and summary reports. Use API analysis to identify and correct common errors and inconsistencies in your API definitions.
 
-> [!NOTE]
-> With managed linting and analysis, API Center sets up a linting engine and any required dependencies and triggers. You can also enable linting and analysis [manually](enable-api-analysis-linting.md). 
+> [!IMPORTANT]
+> Managed API analysis in API Center sets up a linting engine and necessary dependencies automatically. You can also enable linting and analysis [manually](enable-api-analysis-linting.md) using a custom Azure function. **Disable any function used for manual linting before enabling managed API analysis.**
+
 
 In this scenario:
 
@@ -29,6 +30,9 @@ 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
 
 ## Prerequisites
 

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

@@ -23,6 +23,7 @@ ms.custom: Include file
 | 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  |
 
 <sup>1</sup> To increase a limit in the Standard plan, contact [support](https://azure.microsoft.com/support/options/).<br/>
 <sup>2</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/>

articles/chaos-studio/chaos-studio-chaos-experiments.md

@@ -33,22 +33,21 @@ Chaos experiments can target resources in a different subscription than the expe
 
 ## Documenting chaos experiments
 
-There are several methods for documenting chaos engineering. One approach is to use work items in Azure DevOps Boards or in GitHub Projects. By creating dedicated work items for each experiment, you can track the details, progress, and outcomes of your experiments in a structured manner. This documentation can include information such as the purpose of the experiment, the expected outcomes, the steps followed, the resources involved, and any observations or learnings from the experiment.
-
-| Aspect         | Details                                                                                | Description     |
-|----------------|-------------------------------------------------------------------------------------------|-----------------|
-| Hypothesis     | Define the objective and expected outcomes of the experiment                              |                 |
-| Attack Layer   | Identify which part of the system will be subjected to chaos experiments (e.g., network, database, application layer). |                 |
-| Duration       | Specify the time frame for the chaos experiment.                                          |                 |
-| Target         | Determine the specific targets or components within the system.                           |                 |
-| Environment    | Define whether the experiment will be conducted in a production, staging, or development environment. |                 |
-| Observations   | Record any data or behavior observed during the experiment.                               |                 |
-| Results        | Summarize the findings and outcomes of the experiment.                                    |                 |
-| Action Items   | List any action items or steps to be taken based on the results.                          |                 |
-|                |                                                                                           |                 |
-
-The hypothesis is a crucial aspect of a chaos experiment as it defines the objective and expected outcomes of the experiment. It helps in testing the system's ability to handle unexpected disruptions effectively. By formulating a clear hypothesis, you can focus your experiment on specific areas of the system and gather meaningful data to evaluate its resilience. 
-By leveraging the features of Azure DevOps Boards or GitHub Projects, you can collaborate with your team, assign tasks, set due dates, and track the overall progress of your chaos engineering initiatives. This documentation serves as a reference for future analysis, sharing knowledge, and improving the resilience of your systems.
+There are several key aspects of your chaos experimentation process you can track and modify over time. One approach is to use work items in Azure Boards or in GitHub Projects. By creating dedicated work items for each experiment, you can track the details, progress, and outcomes of your experiments in a structured manner. This documentation can include information such as the purpose of the experiment, the expected outcomes, the steps followed, the resources involved, and any observations or learnings from the experiment.
+
+| Item         | Details                                                                                |
+|----------------|-------------------------------------------------------------------------------------------|
+| Hypothesis     | Define the objective and expected outcomes of the experiment                              |
+| Target Scope   | Identify which part of the system will be subjected to chaos experiments (e.g., network, database, application layer). |
+| Duration       | Specify the time frame for the chaos experiment.                                          |
+| Target         | Determine the specific targets or components within the system.                           |
+| Environment    | Define whether the experiment will be conducted in a production, staging, or development environment. |
+| Observations   | Record any data or behavior observed during the experiment.                               |
+| Results        | Summarize the findings and outcomes of the experiment.                                    |
+| Action Items   | List any action items or steps to be taken based on the results.                          |
+|                |                                                                                           |
+
+The **hypothesis** is a crucial aspect of a chaos experiment as it defines the objective and expected outcomes of the experiment. It helps in testing the system's ability to handle unexpected disruptions effectively. By formulating a clear hypothesis, you can focus your experiment on specific areas of the system and gather meaningful data to evaluate its resilience. By leveraging the features of Azure Boards or GitHub Projects, you can collaborate with your team, assign tasks, set due dates, and track the overall progress of your chaos engineering initiatives.
 
 ## Next steps
 Now that you understand what a chaos experiment is you're ready to:

articles/communication-services/quickstarts/voice-video-calling/includes/video-effects/video-effects-javascript.md

@@ -19,22 +19,18 @@ You can use the Video effects feature to add effects to your video in video call
 
 ## Using video effects
 ### Install the package
-Use the `npm install` command to install the Azure Communication Services Effects SDK for JavaScript.
+> [!NOTE]
+> Background blur and background replacement for **Web Desktop browsers** is in GA availability. This quickstart uses the Azure Communication Services Calling SDK version of `1.13.1` (or greater) and the Azure Communication Services Calling Effects SDK version greater than or equil to `1.0.1`. Currently desktop browser support for creating video background effects is only supported on Chrome and Edge Desktop Browser (Windows and Mac) and Mac Safari Desktop.
 
 > [!IMPORTANT]
-> This quickstart uses the Azure Communication Services Calling SDK version of `1.13.1` (or greater) and the Azure Communication Services Calling Effects SDK version greater than or equil to `1.0.1`.
+> Background blur and replacement for **Android Chrome mobile browser** is available in public preview starting in build [1.29.1](https://github.com/Azure/Communication/blob/master/releasenotes/acs-javascript-calling-library-release-notes.md#1291-beta1-2024-08-26) and later beta WebJS SDK versions. This preview version is provided without a service-level agreement, and we don't recommend it for production workloads. Certain features might not be supported or might have constrained capabilities. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
 
-[!INCLUDE [Public Preview Disclaimer](../../../../includes/public-preview-include-document.md)]
-> [!IMPORTANT]
-> Background blur support for Android Chrome mobile browser has been added in build 1.29.1 beta.
+Use the `npm install` command to install the Azure Communication Services Effects SDK for JavaScript.
 
 ```console
 npm install @azure/communication-calling-effects --save
 ```
-See [here](https://www.npmjs.com/package/@azure/communication-calling-effects) for more details on the calling commmunication effects npm package page.
-
-> [!NOTE]
-> Currently browser support for creating video background effects is only supported on Chrome and Edge Desktop Browser (Windows and Mac) and Mac Safari Desktop.
+See [here](https://www.npmjs.com/package/@azure/communication-calling-effects) for more details on the calling communication effects npm package page.
 
 > [!NOTE]
 > Currently there are two available video effects:
@@ -126,7 +122,7 @@ await videoEffectsFeatureApi.startEffects(backgroundBlurEffect);
 await videoEffectsFeatureApi.startEffects(backgroundReplacementEffect);
 ```
 
-At anytime if you want to check what effects are active, you can use the `activeEffects` property.
+At any time if you want to check what effects are active, you can use the `activeEffects` property.
 The `activeEffects` property returns an array with the names of the current active effects, and returns an empty array if there are no effects active.
 ```js
 // Using the video effects feature api