Skip to content

Commit b3bf986

Browse files
authored
Merge pull request #306801 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
2 parents 5a7109d + 77ed1c6 commit b3bf986

4 files changed

Lines changed: 43 additions & 2 deletions

File tree

articles/app-service/environment/app-service-app-service-environment-custom-settings.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -103,6 +103,23 @@ To configure your App Service Environment to use just the ciphers that it requir
103103
> [!WARNING]
104104
> If incorrect values are set for the cipher suite that SChannel can't understand, all TLS communication to your server might stop functioning. In such a case, you'll need to remove the *FrontEndSSLCipherSuiteOrder* entry from **clusterSettings** and submit the updated Resource Manager template to revert back to the default cipher suite settings. Use this functionality with caution.
105105
106+
## Enable FIPS mode
107+
108+
This setting applies to Linux-based workloads in your App Service Environment. You can configure your Linux-based workloads running on App Service Environment to operate in FIPS (Federal Information Processing Standards) mode. When enabled, FIPS mode ensures that cryptographic operations comply with FIPS 140-2 standards.
109+
110+
To enable FIPS mode on your App Service Environment, you can set the following **clusterSettings** entry:
111+
112+
```json
113+
"clusterSettings": [
114+
{
115+
"name": "LinuxFipsModeEnabled",
116+
"value": "true"
117+
}
118+
],
119+
```
120+
121+
When LinuxFipsModeEnabled is set to true, your App Service Environment uses FIPS-compliant cryptographic modules for cryptographic operations.
122+
106123
## Get started
107124

108125
The Azure Quickstart Resource Manager template site includes a template with the base definition for [creating an App Service Environment](https://azure.microsoft.com/resources/templates/web-app-asp-app-on-asev3-create/).

articles/communication-services/quickstarts/voice-video-calling/optimizing-video-placement.md

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -82,6 +82,29 @@ When there's a change in the optimal video count value, if the result indicates
8282

8383
Conversely, if the optimal count decreases and is [less than the current number of videos on the page](../../resources/troubleshooting/voice-video-calling/video-issues/reaching-max-number-of-active-video-subscriptions.md), consider disposing of a video using the dispose method and updating the application layout accordingly.
8484

85+
#### Optimal video count changed reason
86+
87+
When the SDK adjusts the number of rendered video streams, developers can see why the change occurred. The `optimalVideoCountChanged` event includes a `reason` property, helping you adapt UI and troubleshoot quality issues.
88+
89+
Supported reasons:
90+
- Bandwidth – Network limitations
91+
- Performance – Device constraints
92+
93+
Examples:
94+
```javascript
95+
const ovcFeature = this.call.feature(Features.OptimalVideoCount);
96+
97+
// Shows the optimalVideoCount value
98+
console.log(ovcFeature.optimalVideoCount);
99+
100+
// shows the last reason for a change
101+
console.log(ovcFeature.lastOvcChangeReason);
102+
103+
// listener for getting updates on changes
104+
ovcFeature.on('optimalVideoCountChanged', () => {});
105+
```
106+
107+
85108
### Things to consider when adding a 1080p or 720p video to a page.
86109

87110
- You can place one 1080p incoming video with the rest smaller than 720p.
@@ -193,6 +216,7 @@ The following table illustrates how video resolution changes based on the number
193216
> [!NOTE]
194217
> The public preview 1.37.1-beta.1 and greater of the calling WebJS SDK currently supports up to **25** incoming video streams for desktop browsers (5x5 grid).
195218
219+
196220
## Conclusion
197221

198222
To determine how many videos to place on a web page, you need to carefully consider resolution, device type, bandwidth, and user experience. Follow these guidelines and best practices to create web apps that not only look appealing but also function seamlessly, providing an optimal viewing experience for users across various devices and connection speeds.

articles/role-based-access-control/built-in-roles.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -191,7 +191,7 @@ The following table provides a brief description of each built-in role. Click th
191191
> | Built-in role | Description | ID |
192192
> | --- | --- | --- |
193193
> | <a name='acrdelete'></a>[AcrDelete](./built-in-roles/containers.md#acrdelete) | Delete repositories, tags, or manifests from a container registry. | c2f4ef07-c644-48eb-af81-4b1b4947fb11 |
194-
> | <a name='acrimagesigner'></a>[AcrImageSigner](./built-in-roles/containers.md#acrimagesigner) | Push trusted images to or pull trusted images from a container registry enabled for content trust. | 6cef56e8-d556-48e5-a04f-b8e64114680f |
194+
> | <a name='acrimagesigner'></a>[AcrImageSigner](./built-in-roles/containers.md#acrimagesigner) | Avoid using this role. Content Trust in Azure Container Registry and the AcrImageSigner role are being deprecated and will be completely removed on March 31, 2028. For details and transition guidance, see https://aka.ms/acr/dctdeprecation. | 6cef56e8-d556-48e5-a04f-b8e64114680f |
195195
> | <a name='acrpull'></a>[AcrPull](./built-in-roles/containers.md#acrpull) | Pull artifacts from a container registry. | 7f951dda-4ed3-4680-a7ca-43fe172d538d |
196196
> | <a name='acrpush'></a>[AcrPush](./built-in-roles/containers.md#acrpush) | Push artifacts to or pull artifacts from a container registry. | 8311e382-0749-4cb8-b61a-304f252e45ec |
197197
> | <a name='acrquarantinereader'></a>[AcrQuarantineReader](./built-in-roles/containers.md#acrquarantinereader) | Pull quarantined images from a container registry. | cdda3590-29a3-44f6-95f2-9f980659eb04 |

articles/role-based-access-control/built-in-roles/containers.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ Delete repositories, tags, or manifests from a container registry.
5959

6060
## AcrImageSigner
6161

62-
Push trusted images to or pull trusted images from a container registry enabled for content trust.
62+
Avoid using this role. Content Trust in Azure Container Registry and the AcrImageSigner role are being deprecated and will be completely removed on March 31, 2028. For details and transition guidance, see https://aka.ms/acr/dctdeprecation.
6363

6464
[Learn more](/azure/container-registry/container-registry-rbac-built-in-roles-directory-reference)
6565

0 commit comments

Comments
 (0)