Skip to content

Commit 8cf4319

Browse files
authored
Merge pull request #213404 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 e47b3ad + 257b29f commit 8cf4319

File tree

9 files changed

+62
-33
lines changed

9 files changed

+62
-33
lines changed

articles/active-directory/authentication/howto-authentication-temporary-access-pass.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -71,9 +71,9 @@ To configure the Temporary Access Pass authentication method policy:
7171
After you enable a policy, you can create a Temporary Access Pass for a user in Azure AD.
7272
These roles can perform the following actions related to a Temporary Access Pass.
7373

74-
- Global Administrator can create, delete, view a Temporary Access Pass on any user (except themselves)
75-
- Privileged Authentication Administrators can create, delete, view a Temporary Access Pass on admins and members (except themselves)
76-
- Authentication Administrators can create, delete, view a Temporary Access Pass on members (except themselves)
74+
- Global Administrators can create, delete, and view a Temporary Access Pass on any user (except themselves)
75+
- Privileged Authentication Administrators can create, delete, and view a Temporary Access Pass on admins and members (except themselves)
76+
- Authentication Administrators can create, delete, and view a Temporary Access Pass on members (except themselves)
7777
- Global Reader can view the Temporary Access Pass details on the user (without reading the code itself).
7878

7979
1. Sign in to the Azure portal as either a Global administrator, Privileged Authentication administrator, or Authentication administrator.

articles/active-directory/hybrid/how-to-connect-group-writeback-enable.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,8 @@ Group writeback requires enabling both the original and new versions of the feat
2626

2727
> [!NOTE]
2828
> We recommend that you follow the [swing migration](how-to-upgrade-previous-version.md#swing-migration) method for rolling out the new group writeback feature in your environment. This method will provide a clear contingency plan if a major rollback is necessary.
29+
>
30+
>The enhanced group writeback feature is enabled on the tenant and not per Azure AD Connect client instance. Please be sure that all Azure AD Connect client instances are updated to a minimal build version of 1.6.4.0 or later.
2931
3032
### Enable group writeback by using PowerShell
3133

articles/communication-services/concepts/voice-video-calling/calling-sdk-features.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,7 @@ The Communication Services Calling SDK supports the following streaming configur
8383

8484
| Limit | Web | Windows/Android/iOS |
8585
| ------------------------------------------------------------- | --------------------------- | -------------------------- |
86-
| **Maximum # of outgoing local streams that can be sent simultaneously** | 1 video or 1 screen sharing | 1 video + 1 screen sharing |
86+
| **Maximum # of outgoing local streams that can be sent simultaneously** | 1 video and 1 screen sharing | 1 video + 1 screen sharing |
8787
| **Maximum # of incoming remote streams that can be rendered simultaneously** | 4 videos + 1 screen sharing | 6 videos + 1 screen sharing |
8888

8989
While the Calling SDK won't enforce these limits, your users may experience performance degradation if they're exceeded.

articles/communication-services/how-tos/calling-sdk/includes/manage-video/manage-video-web.md

Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -144,6 +144,55 @@ If the specified video device is being used by another process, or if it is disa
144144
- A call to the `localVideoStream.switchSource()` method will cause `cameraStartFailed` to be set to true.
145145
Our Call Diagnostics guide provides additional information on how to diagnose call related issues.
146146

147+
To check or verify if the local video is on or off, you can use isLocalVideoStarted API which returns true or false:
148+
```js
149+
// Check if local video is on or off
150+
call.isLocalVideoStarted;
151+
```
152+
153+
To listen for changes to the local video, you can subscribe and unsubscribe to the isLocalVideoStartedChanged event
154+
```js
155+
// Subscribe to local video event
156+
call.on('isLocalVideoStartedChanged', () => {
157+
// Callback();
158+
});
159+
// Unsubscribe from local video event
160+
call.off('isLocalVideoStartedChanged', () => {
161+
// Callback();
162+
});
163+
```
164+
165+
166+
167+
## Start and stop screen sharing while on a call
168+
To start and stop screen sharing while on a call, you can use asynchronous APIs startScreenSharing and stopScreenSharing respectively:
169+
170+
```js
171+
// Start screen sharing
172+
await call.startScreenSharing();
173+
174+
// Stop screen sharing
175+
await call.stopScreenSharing();
176+
```
177+
178+
To check or verify if screen sharing is on or off, you can use isScreenSharingOn API which returns true or false:
179+
```js
180+
// Check if screen sharing is on or off
181+
call.isScreenSharingOn;
182+
```
183+
184+
To listen for changes to the screen share, you can subscribe and unsubscribe to the isScreenSharingOnChanged event
185+
```js
186+
// Subscribe to screen share event
187+
call.on('isScreenSharingOnChanged', () => {
188+
// Callback();
189+
});
190+
// Unsubscribe from screen share event
191+
call.off('isScreenSharingOnChanged', () => {
192+
// Callback();
193+
});
194+
```
195+
147196
## Render remote participant video streams
148197

149198
To list the video streams and screen sharing streams of remote participants, inspect the `videoStreams` collections:

articles/communication-services/tutorials/virtual-visits.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -104,9 +104,7 @@ Opening the App Service’s URL and navigating to `https://<YOUR URL>/VISIT` all
104104

105105
### Step 5 - Set deployed app URL in Bookings
106106

107-
Copy your application url into your calendar Business information setting by going to https://outlook.office.com/bookings/businessinformation.
108-
109-
![Screenshot of final view of bookings business information.](./media/virtual-visits/bookings-acs-app-integration-url.png)
107+
Enter the application url followed by "/visit" in the "Deployed App URL" field in https://outlook.office.com/bookings/businessinformation.
110108

111109
## Going to production
112110
The Sample Builder gives you the basics of a Microsoft 365 and Azure virtual visit: consumer scheduling via Bookings, consumer joins via custom app, and the provider joins via Teams. However, there are several things to consider as you take this scenario to production.

articles/load-balancer/ipv6-dual-stack-standard-internal-load-balancer-powershell.md

Lines changed: 0 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -38,26 +38,6 @@ The changes that make the above an internal load balancer front-end configuratio
3838

3939
If you choose to install and use PowerShell locally, this article requires the Azure PowerShell module version 6.9.0 or later. Run `Get-Module -ListAvailable Az` to find the installed version. If you need to upgrade, see [Install Azure PowerShell module](/powershell/azure/install-Az-ps). If you are running PowerShell locally, you also need to run `Connect-AzAccount` to create a connection with Azure.
4040

41-
## Prerequisites
42-
Before you deploy a dual stack application in Azure, you must configure your subscription for this preview feature using the following Azure PowerShell:
43-
44-
Register as follows:
45-
```azurepowershell
46-
Register-AzProviderFeature -FeatureName AllowIPv6VirtualNetwork -ProviderNamespace Microsoft.Network
47-
Register-AzProviderFeature -FeatureName AllowIPv6CAOnStandardLB -ProviderNamespace Microsoft.Network
48-
```
49-
It takes up to 30 minutes for feature registration to complete. You can check your registration status by running the following Azure PowerShell command:
50-
Check on the registration as follows:
51-
```azurepowershell
52-
Get-AzProviderFeature -FeatureName AllowIPv6VirtualNetwork -ProviderNamespace Microsoft.Network
53-
Get-AzProviderFeature -FeatureName AllowIPv6CAOnStandardLB -ProviderNamespace Microsoft.Network
54-
```
55-
After the registration is complete, run the following command:
56-
57-
```azurepowershell
58-
Register-AzResourceProvider -ProviderNamespace Microsoft.Network
59-
```
60-
6141
## Create a resource group
6242

6343
Before you can create your dual-stack virtual network, you must create a resource group with [New-AzResourceGroup](/powershell/module/az.resources/new-azresourcegroup). The following example creates a resource group named *dsStd_ILB_RG* in the *east us* location:

articles/postgresql/flexible-server/overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -117,7 +117,7 @@ One advantage of running your workload in Azure is global reach. The flexible se
117117
| North Europe | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
118118
| Norway East | :heavy_check_mark: | :x: | :x: |
119119
| Qatar Central | :heavy_check_mark: | :x: | :x: |
120-
| South Africa North | :heavy_check_mark: | :heavy_check_mark: | :x: |
120+
| South Africa North | :heavy_check_mark: | :heavy_check_mark: ** | :x: |
121121
| South Central US | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark: |
122122
| South India | :x: $$ | :x: | :heavy_check_mark: |
123123
| Southeast Asia | :heavy_check_mark: | :x: $ | :heavy_check_mark: |

articles/purview/includes/access-policies-configuration-generic.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,9 +11,9 @@ ms.custom:
1111
### Register Microsoft Purview as a resource provider in other subscriptions
1212
Execute this step only if the data sources and the Microsoft Purview account are in different subscriptions. Register Microsoft Purview as a resource provider in each subscription where data sources reside by following this guide: [Register resource provider](../../azure-resource-manager/management/resource-providers-and-types.md#register-resource-provider).
1313

14-
The Microsoft Purview resource provider is:
14+
The Microsoft Purview resource provider is: Microsoft.Purview. To register using Powershell run the below:
1515
```
16-
Microsoft.Purview
16+
Register-AzResourceProvider -ProviderNamespace Microsoft.Purview
1717
```
1818

1919
### Configure permissions for policy management actions

articles/purview/tutorial-data-owner-policies-storage.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ To register your resource and enable Data Use Management, follow these steps:
6161

6262
1. If you have a firewall enabled on your Storage account, follow these steps as well:
6363
1. Go into your Azure Storage account in [Azure portal](https://portal.azure.com).
64-
1. Navigate to **Security + networking > Networking**.NET
64+
1. Navigate to **Security + networking > Networking**.
6565
1. Choose **Selected Networks** under **Allow access from**.
6666
1. In the **Exceptions** section, select **Allow trusted Microsoft services to access this storage account** and select **Save**.
6767

@@ -131,7 +131,7 @@ To register your resource and enable Data Use Management, follow these steps:
131131

132132
:::image type="content" source="./media/how-to-policies-data-owner-authoring-generic/select-data-source-type.png" alt-text="Screenshot showing the policy editor, with Data Resources selected, and Data source Type highlighted in the data resources menu.":::
133133

134-
1. Select the **Continue** button and transverse the hierarchy to select and underlying data-object (for example: folder, file, etc.). Select **Recursive** to apply the policy from that point in the hierarchy down to any child data-objects. Then select the **Add** button. This will take you back to the policy editor.
134+
1. Select the **Continue** button and traverse the hierarchy to select and underlying data-object (for example: folder, file, etc.). Select **Recursive** to apply the policy from that point in the hierarchy down to any child data-objects. Then select the **Add** button. This will take you back to the policy editor.
135135

136136
:::image type="content" source="./media/how-to-policies-data-owner-authoring-generic/select-asset.png" alt-text="Screenshot showing the Select asset menu, and the Add button highlighted.":::
137137

@@ -188,4 +188,4 @@ Check our demo and related tutorials:
188188
> [!div class="nextstepaction"]
189189
> [Demo of access policy for Azure Storage](https://learn-video.azurefd.net/vod/player?id=caa25ad3-7927-4dcc-88dd-6b74bcae98a2)
190190
> [Concepts for Microsoft Purview data owner policies](./concept-policies-data-owner.md)
191-
> [Enable Microsoft Purview data owner policies on all data sources in a subscription or a resource group](./how-to-policies-data-owner-resource-group.md)
191+
> [Enable Microsoft Purview data owner policies on all data sources in a subscription or a resource group](./how-to-policies-data-owner-resource-group.md)

0 commit comments

Comments
 (0)