You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -446,7 +446,8 @@ Here, you can configure some common settings for the app. Some settings require
446
446
-**Always On**: Keeps the app loaded even when there's no traffic. When **Always On** isn't turned on (default), the app is unloaded after 20 minutes without any incoming requests. The unloaded app can cause high latency for new requests because of its warm-up time. When **Always On** is turned on, the front-end load balancer sends a GET request to the application root every five minutes. The continuous ping prevents the app from being unloaded.
447
447
448
448
Always On is required for continuous WebJobs or for WebJobs that are triggered using a CRON expression.
449
-
-**ARR affinity**: In a multi-instance deployment, ensure that the client is routed to the same instance for the life of the session. You can set this option to **Off** for stateless applications.
449
+
-**Session affinity**: In a multi-instance deployment, ensure that the client is routed to the same instance for the life of the session. You can set this option to **Off** for stateless applications.
450
+
-**Session affinity proxy**: Session affinity proxy can be turned on if your app is behind a reverse proxy (like Azure Application Gateway or Azure Front Door) and you are using the default host name. The domain for the session affinity cookie will align with the forwarded host name from the reverse proxy.
450
451
-**HTTPS Only**: When enabled, all HTTP traffic is redirected to HTTPS.
451
452
-**Minimum TLS version**: Select the minimum TLS encryption version required by your app.
452
453
-**Debugging**: Enable remote debugging for [ASP.NET](troubleshoot-dotnet-visual-studio.md#remotedebug), [ASP.NET Core](/visualstudio/debugger/remote-debugging-azure), or [Node.js](configure-language-nodejs.md#debug-remotely) apps. This option turns off automatically after 48 hours.
Copy file name to clipboardExpand all lines: articles/app-service/overview-tls.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,6 +29,17 @@ Transport Layer Security (TLS) is a widely adopted security protocol designed to
29
29
30
30
For incoming requests to your web app, App Service supports TLS versions 1.0, 1.1, 1.2, and 1.3.
31
31
32
+
### Set Minimum TLS Version
33
+
Follow these steps to change the Minimum TLS version of your App Service resource:
34
+
1. Browse to your app in the [Azure portal](https://portal.azure.com/)
35
+
1. In the left menu, select **configuration** and then select the **General settings** tab.
36
+
1. On __Minimum Inbound TLS Version__, using the dropdown, select your desired version.
37
+
1. Select **Save** to save the changes.
38
+
39
+
### Minimum TLS Version with Azure Policy
40
+
41
+
You can use Azure Policy to help audit your resources when it comes to minimum TLS version. You can refer to [App Service apps should use the latest TLS version policy definition](https://ms.portal.azure.com/#view/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Ff0e6e85b-9b9f-4a4b-b67b-f730d42f1b0b) and change the values to your desired minimum TLS version. For similar policy definitions for other App Service resources, refer to [List of built-in policy definitions - Azure Policy for App Service](../governance/policy/samples/built-in-policies.md#app-service).
42
+
32
43
### Minimum TLS Version and SCM Minimum TLS Version
33
44
34
45
App Service also allows you to set minimum TLS version for incoming requests to your web app and to SCM site. By default, the minimum TLS version for incoming requests to your web app and to SCM would be set to 1.2 on both portal and API.
Any participant in the call or meeting can be pinned. Only Microsoft 365 users who have an organizer, co-organizer or presenter role can start spotlight for other participants. This action is idempotent, trying to start spotlight on a pinned participant does nothing
46
25
47
-
To use this feature, a list of participants identifiers is required
26
+
### Start spotlight for participants
27
+
28
+
Any participant in the call or meeting can be pinned. Only Microsoft 365 users who have an organizer, co-organizer, or presenter role can start spotlight for other participants. This action is idempotent, trying to start spotlight on a pinned participant does nothing
29
+
30
+
You need a list of participant identifiers to use this feature.
Any pinned participant in the call or meeting can be unpinned. Only Microsoft 365 users who have an organizer, co-organizer or presenter role can unpin other participants. This action is idempotent, trying to stop spotlight on an unpinned participant does nothing
65
50
66
-
To use this feature, a list of participants identifiers is required
51
+
Any pinned participant in the call or meeting can be unpinned. Only Microsoft 365 users who have an organizer, co-organizer, or presenter role can unpin other participants. This action is idempotent, trying to stop spotlight on an unpinned participant does nothing.
52
+
53
+
You need a list of participants identifiers to use this feature.
All pinned participants can be unpinned using this API. Only MicrosoftTeamsUserIdentifier users who have an organizer, co-organizer or presenter role can unpin all participants.
73
+
74
+
All pinned participants can be unpinned using this operation. Only `MicrosoftTeamsUserIdentifier` users who have an organizer, co-organizer, or presenter role can unpin all participants.
75
+
83
76
```java
84
77
spotlightCallFeature.stopAllSpotlight();
85
78
```
86
79
87
80
### Handle changed states
88
-
The `Spotlight` API allows you to subscribe to `SpotlightChanged` events. A `SpotlightChanged` event comes from a `call` instance and contains information about newly spotlighted participants and participants whose spotlight were stopped
81
+
82
+
Spotlight mode enables you to subscribe to `SpotlightChanged` events. A `SpotlightChanged` event comes from a call instance and contains information about newly spotlighted participants and participants whose spotlight stopped. The returned array `SpotlightedParticipant` is sorted by the order the participants were spotlighted.
83
+
84
+
To get information about all participants with spotlight state changes on the current call, use the following code.
To get information about all participants that have spotlight state on current call, you can use the following API. The returned array is sorted by the order the participants were spotlighted.
106
+
### Get all spotlighted participants
107
+
108
+
To get information about all participants that have spotlight state on current call, use the following operation. The returned array is sorted by the order the participants were spotlighted.
Any participant in the call or meeting can be pinned. Only Microsoft 365 users who have an organizer, co-organizer or presenter role can start spotlight for other participants. This action is idempotent, trying to start spotlight on a pinned participant does nothing
26
+
### Start spotlight for participants
48
27
49
-
To use this feature, a list of participants identifiers is required
28
+
Any participant in the call or meeting can be pinned. Only Microsoft 365 users who have an organizer, co-organizer, or presenter role can start spotlight for other participants. This action is idempotent, trying to start spotlight on a pinned participant does nothing
29
+
30
+
You need a list of participant identifiers to use this feature.
Any pinned participant in the call or meeting can be unpinned. Only Microsoft 365 users who have an organizer, co-organizer or presenter role can unpin other participants. This action is idempotent, trying to stop spotlight on an unpinned participant does nothing
64
44
65
-
To use this feature, a list of participants identifiers is required
45
+
Any pinned participant in the call or meeting can be unpinned. Only Microsoft 365 users who have an organizer, co-organizer, or presenter role can unpin other participants. This action is idempotent, trying to stop spotlight on an unpinned participant does nothing.
46
+
47
+
You need a list of participants identifiers to use this feature.
All pinned participants can be unpinned using this API. Only MicrosoftTeamsUserIdentifier users who have an organizer, co-organizer or presenter role can unpin all participants.
61
+
62
+
All pinned participants can be unpinned using this operation. Only `MicrosoftTeamsUserIdentifier` users who have an organizer, co-organizer, or presenter role can unpin all participants.
63
+
79
64
```swift
80
65
spotlightFeature.stopAllSpotlight(completionHandler: { (error) in
81
66
iflet error = error {
@@ -85,7 +70,11 @@ spotlightFeature.stopAllSpotlight(completionHandler: { (error) in
85
70
```
86
71
87
72
### Handle changed states
88
-
The `Spotlight` API allows you to subscribe to `SpotlightChanged` events. A `SpotlightChanged` event comes from a `call` instance and contains information about newly spotlighted participants and participants whose spotlight were stopped
73
+
74
+
Spotlight mode enables you to subscribe to `SpotlightChanged` events. A `SpotlightChanged` event comes from a call instance and contains information about newly spotlighted participants and participants whose spotlight stopped. The returned array `SpotlightedParticipant` is sorted by the order the participants were spotlighted.
75
+
76
+
To get information about all participants with spotlight state changes on the current call, use the following code.
@@ -107,17 +96,20 @@ public class SpotlightDelegate: SpotlightCallFeatureDelegate {
107
96
}
108
97
```
109
98
110
-
### Get all spotlighted participants:
111
-
To get information about all participants that have spotlight state on current call, you can use the following API. The returned array is sorted by the order the participants were spotlighted.
99
+
### Get all spotlighted participants
100
+
101
+
To get information about all participants that have spotlight state on the current call, use the following operation. The returned array is sorted by the order the participants were spotlighted.
112
102
113
103
```swift
114
104
spotlightCallFeature.spotlightedParticipants.forEach { participant in
115
105
print("Spotlight active for participant: "+ Utilities.toMri(participant.identifier))
116
106
}
117
107
```
118
108
119
-
### Get the maximum supported spotlight:
120
-
The following API can be used to get the maximum number of participants that can be spotlighted using the Calling SDK
109
+
### Get the maximum supported spotlight participants
110
+
111
+
Use the following operation to get the maximum number of participants that can be spotlighted using the Calling SDK.
0 commit comments