Skip to content

Commit 73f6e1b

Browse files
authored
Merge pull request #164459 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to master to sync with https://github.com/MicrosoftDocs/azure-docs (branch master)
2 parents b6f7dab + c98bf6d commit 73f6e1b

File tree

9 files changed

+48
-31
lines changed

9 files changed

+48
-31
lines changed

articles/communication-services/concepts/known-issues.md

Lines changed: 35 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -11,18 +11,19 @@ ms.topic: troubleshooting
1111
ms.service: azure-communication-services
1212
---
1313

14-
# Known issues: Azure Communication Services Calling SDKs
15-
This article provides information about limitations and known issues related to the Azure Communication Services Calling SDKs.
14+
# Known issues
15+
This article provides information about limitations and known issues related to the Azure Communication Services Calling SDKs and Azure Communication Services Call Automation APIs
1616

1717
> [!IMPORTANT]
1818
> There are multiple factors that can affect the quality of your calling experience. Refer to the **[network requirements](./voice-video-calling/network-requirements.md)** documentation to learn more about Communication Services network configuration and testing best practices.
1919
20+
## Azure Communication Services Calling SDKs
2021

21-
## JavaScript SDK
22+
### JavaScript SDK
2223

2324
This section provides information about known issues associated with the Azure Communication Services JavaScript voice and video calling SDKs.
2425

25-
### Refreshing a page doesn't immediately remove the user from their call
26+
#### Refreshing a page doesn't immediately remove the user from their call
2627

2728
If a user is in a call and decides to refresh the page, the Communication Services media service won't remove this user immediately from the call. It will wait for the user to rejoin. The user will be removed from the call after the media service times out.
2829

@@ -35,16 +36,16 @@ If the user rejoins with the same Communication Services user ID, they'll be rep
3536
If the user was sending video before refreshing, the `videoStreams` collection will keep the previous stream information until the service times out and removes it. In this scenario, the application may decide to observe any new streams added to the collection and render one with the highest `id`.
3637

3738

38-
### It's not possible to render multiple previews from multiple devices on web
39+
#### It's not possible to render multiple previews from multiple devices on web
3940
This is a known limitation. For more information, see the [calling SDK overview](./voice-video-calling/calling-sdk-features.md).
4041

41-
### Enumerating devices isn't possible in Safari when the application runs on iOS or iPadOS
42+
#### Enumerating devices isn't possible in Safari when the application runs on iOS or iPadOS
4243

4344
Applications can't enumerate/select mic/speaker devices (like Bluetooth) on Safari iOS/iPad. This is a known operating system limitation.
4445

4546
If you're using Safari on macOS, your app won't be able to enumerate/select speakers through the Communication Services Device Manager. In this scenario, devices must be selected via the OS. If you use Chrome on macOS, the app can enumerate/select devices through the Communication Services Device Manager.
4647

47-
### Audio connectivity is lost when receiving SMS messages or calls during an ongoing VoIP call
48+
#### Audio connectivity is lost when receiving SMS messages or calls during an ongoing VoIP call
4849
This problem may occur due to multiple reasons:
4950

5051
- Some mobile browsers don't maintain connectivity while in the background state. This can lead to a degraded call experience if the VoIP call was interrupted by an event that pushes your application into the background.
@@ -54,22 +55,22 @@ This problem may occur due to multiple reasons:
5455
<br/>Browsers: Safari, Chrome
5556
<br/>Operating System: iOS, Android
5657

57-
### Repeatedly switching video devices may cause video streaming to temporarily stop
58+
#### Repeatedly switching video devices may cause video streaming to temporarily stop
5859

5960
Switching between video devices may cause your video stream to pause while the stream is acquired from the selected device.
6061

61-
#### Possible causes
62+
##### Possible causes
6263
Switching between devices frequently can cause performance degradation. Developers are encouraged to stop one device stream before starting another.
6364

64-
### Bluetooth headset microphone is not detected therefore is not audible during the call on Safari on iOS
65+
#### Bluetooth headset microphone is not detected therefore is not audible during the call on Safari on iOS
6566
Bluetooth headsets aren't supported by Safari on iOS. Your Bluetooth device won't be listed in available microphone options and other participants won't be able to hear you if you try using Bluetooth over Safari.
6667

67-
#### Possible causes
68+
##### Possible causes
6869
This is a known macOS/iOS/iPadOS operating system limitation.
6970

7071
With Safari on **macOS** and **iOS/iPadOS**, it is not possible to enumerating/selecting speaker devices through the Communication Services Device Manager since speakers enumeration/selection is not supported by Safari. In this scenario, your device selection should be updated via the operating system.
7172

72-
### Rotation of a device can create poor video quality
73+
#### Rotation of a device can create poor video quality
7374
Users may experience degraded video quality when devices are rotated.
7475

7576
<br/>Devices affected: Google Pixel 5, Google Pixel 3a, Apple iPad 8, and Apple iPad X
@@ -78,7 +79,7 @@ Users may experience degraded video quality when devices are rotated.
7879
<br/>Operating System: iOS, Android
7980

8081

81-
### Camera switching makes the screen freeze
82+
#### Camera switching makes the screen freeze
8283
When a Communication Services user joins a call using the JavaScript calling SDK and then hits the camera switch button, the UI may become unresponsive until the application is refreshed or browser is pushed to the background by user.
8384

8485
<br/>Devices affected: Google Pixel 4a
@@ -87,30 +88,30 @@ When a Communication Services user joins a call using the JavaScript calling SDK
8788
<br/>Operating System: iOS, Android
8889

8990

90-
#### Possible causes
91+
##### Possible causes
9192
Under investigation.
9293

93-
### If the video signal was stopped while the call is in "connecting" state, the video will not be sent after the call started
94+
#### If the video signal was stopped while the call is in "connecting" state, the video will not be sent after the call started
9495
If users decide to quickly turn video on/off while call is in `Connecting` state - this may lead to problem with stream acquired for the call. We encourage developers to build their apps in a way that doesn't require video to be turned on/off while call is in `Connecting` state. This issue may cause degraded video performance in the following scenarios:
9596

9697
- If the user starts with audio and then start and stop video while the call is in `Connecting` state.
9798
- If the user starts with audio and then start and stop video while the call is in `Lobby` state.
9899

99-
#### Possible causes
100+
##### Possible causes
100101
Under investigation.
101102

102-
### Enumerating/accessing devices for Safari on MacOS and iOS
103+
#### Enumerating/accessing devices for Safari on MacOS and iOS
103104
If access to devices are granted, after some time, device permissions are reset. Safari on MacOS and on iOS does not keep permissions for very long time unless there is a stream acquired. The simplest way to work around this is to call DeviceManager.askDevicePermission() API before calling the device manager's device enumeration APIs (DeviceManager.getCameras(), DeviceManager.getSpeakers(), and DeviceManager.getMicrophones()). If the permissions are there, then user will not see anything, if not, it will re-prompt.
104105

105106
<br/>Devices affected: iPhone
106107
<br/>Client library: Calling (JavaScript)
107108
<br/>Browsers: Safari
108109
<br/>Operating System: iOS
109110

110-
### Sometimes it takes a long time to render remote participant videos
111+
#### Sometimes it takes a long time to render remote participant videos
111112
During an ongoing group call, _User A_ sends video and then _User B_ joins the call. Sometimes, User B doesn't see video from User A, or User A's video begins rendering after a long delay. This issue could be caused by a network environment that requires further configuration. Refer to the [network requirements](./voice-video-calling/network-requirements.md) documentation for network configuration guidance.
112113

113-
### Using 3rd party libraries to access GUM during the call may result in audio loss
114+
#### Using 3rd party libraries to access GUM during the call may result in audio loss
114115
Using getUserMedia separately inside the application will result in losing audio stream since a third party library takes over device access from ACS library.
115116
Developers are encouraged to do the following:
116117
1. Don't use 3rd party libraries that are using internally GetUserMedia API during the call.
@@ -119,5 +120,19 @@ Developers are encouraged to do the following:
119120
<br/>Browsers: Safari
120121
<br/>Operating System: iOS
121122

122-
#### Possible causes
123+
##### Possible causes
123124
In some browsers (Safari for example), acquiring your own stream from the same device will have a side-effect of running into race conditions. Acquiring streams from other devices may lead the user into insufficient USB/IO bandwidth, and sourceUnavailableError rate will skyrocket.
125+
126+
127+
## Azure Communication Services Call Automation APIs
128+
129+
Following are the known issues in the Azure Communication Services Call Automation APIs
130+
131+
- The only authentication supported at this time for server applications is using a connection string.
132+
133+
- Calls should be make only between entities of the same Azure Communication Service resource. Cross resource communication is blocked.
134+
135+
- Calls between Teams' tenant users and Azure Communication Service user or server application entities are not allowed.
136+
137+
- If an application dials out to two or more PSTN identities and then quits the call, the call between the other PSTN entities would be dropped.
138+

articles/marketplace/azure-app-apis.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.subservice: partnercenter-marketplace-publisher
66
ms.topic: conceptual
77
ms.author: mingshen
88
author: mingshen-ms
9-
ms.date: 06/01/2021
9+
ms.date: 07/01/2021
1010
---
1111

1212
# Partner Center submission API to onboard Azure apps in Partner Center
@@ -69,4 +69,4 @@ https://apidocs.microsoft.com/services/partneringestion/
6969
## Next steps
7070

7171
* [Create an Azure Container technical asset](azure-container-technical-assets.md)
72-
* [Create an Azure Container offer](azure-container-offer-setup.md)
72+
* [Create an Azure Container offer](azure-container-offer-setup.md)

articles/marketplace/azure-app-metered-billing.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: This documentation is a guide for ISVs publishing Azure application
44
ms.service: marketplace
55
ms.subservice: partnercenter-marketplace-publisher
66
ms.topic: conceptual
7-
ms.date: 04/22/2020
7+
ms.date: 07/01/2021
88
ms.author: mingshen
99
author: mingshen-ms
1010
---

articles/marketplace/azure-app-review-feedback.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Handle feedback for your Azure application offer from the Microsoft
44
ms.service: marketplace
55
ms.subservice: partnercenter-marketplace-publisher
66
ms.topic: conceptual
7-
ms.date: 11/11/2019
7+
ms.date: 07/01/2021
88
ms.author: mingshen
99
author: mingshen-ms
1010
---

articles/marketplace/marketplace-solution-templates.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.subservice: partnercenter-marketplace-publisher
66
ms.topic: conceptual
77
author: msjogarrig
88
ms.author: jogarrig
9-
ms.date: 04/22/2020
9+
ms.date: 07/01/2021
1010
---
1111

1212
# Publishing guide for Azure applications solution template offers
@@ -36,4 +36,4 @@ If you haven't already done so, learn how to [Grow your cloud business with Azur
3636
To register for and start working in Partner Center:
3737

3838
- [Sign in to Partner Center](https://partner.microsoft.com/dashboard/account/v3/enrollment/introduction/partnership) to create or complete your offer.
39-
- See [Create an Azure application offer](./azure-app-offer-setup.md) for more information.
39+
- See [Create an Azure application offer](./azure-app-offer-setup.md) for more information.

articles/spring-cloud/access-app-virtual-network.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,9 @@ The following procedure creates a private DNS zone for an application in the pri
2525

2626
3. Fill out the form on the **Create Private DNS zone** page. Enter **<span>private.azuremicroservices.io</span>** as the **Name** of the zone.
2727

28+
>[!NOTE]
29+
> If you are using Azure China, please replace `private.azuremicroservices.io` with `private.microservices.azure.cn` for the whole documentation, [learn more](/azure/china/resources-developer-guide#check-endpoints-in-azure).
30+
2831
4. Select **Review + Create**.
2932

3033
5. Select **Create**.
@@ -119,4 +122,4 @@ After the assignment, you can access the private FQDN of your application in pri
119122
## See also
120123

121124
- [Troubleshooting Azure Spring Cloud in VNET](./troubleshooting-vnet.md)
122-
- [Customer Responsibilities for Running Azure Spring Cloud in VNET](./vnet-customer-responsibilities.md)
125+
- [Customer Responsibilities for Running Azure Spring Cloud in VNET](./vnet-customer-responsibilities.md)

articles/spring-cloud/how-to-deploy-in-azure-virtual-network.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -164,7 +164,7 @@ This table shows the maximum number of app instances Azure Spring Cloud supports
164164
| /25 | 128 | 120 | <p> App with 1 core: 500<br> App with 2 cores: 500<br> App with 3 cores: 480<br> App with 4 cores: 360</p> |
165165
| /24 | 256 | 248 | <p> App with 1 core: 500<br/> App with 2 cores: 500<br/> App with 3 cores: 500<br/> App with 4 cores: 500</p> |
166166
167-
For subnets, five IP addresses are reserved by Azure, and at least three IP addresses are required by Azure Spring Cloud. At least nine IP addresses are required, so /29 and /30 are nonoperational.
167+
For subnets, five IP addresses are reserved by Azure, and at least three IP addresses are required by Azure Spring Cloud. At least eight IP addresses are required, so /29 and /30 are nonoperational.
168168
169169
For a service runtime subnet, the minimum size is /28. This size has no bearing on the number of app instances.
170170

articles/spring-cloud/vnet-customer-responsibilities.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,7 @@ By default, Azure Spring Cloud has unrestricted outbound (egress) internet acces
2121
The following is a list of resource requirements for Azure Spring Cloud services. As a general requirement you should not modify resource groups created by Azure Spring Cloud and the underlying network resources.
2222
- Do not modify resource groups created and owned by Azure Spring Cloud.
2323
- By default, these resource groups are named as ap-svc-rt_[SERVICE-INSTANCE-NAME]_[REGION]* and ap_[SERVICE-INSTANCE-NAME]_[REGION]*.
24+
- Do not block Azure Spring Cloud from updating reseources in these resource groups.
2425
- Do not modify subnets used by Azure Spring Cloud.
2526
- Do not create more than one Azure Spring Cloud service instance in the same subnet.
2627
- When using a firewall to control traffic, *do not* block the following egress traffic to Azure Spring Cloud components that operate, maintain, and support the service instance.

articles/synapse-analytics/security/workspace-data-exfiltration-protection.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -29,9 +29,7 @@ Let us use an example to illustrate data exfiltration protection for Synapse wor
2929

3030
>[!IMPORTANT]
3131
>
32-
> - Resources in tenants other than the workspace's tenant must not have blocking firewall rules in place for the SQL pools to connect to them. Resources within the workspace’s managed virtual network, such as Spark clusters, can connect over managed private links to firewall-protected resources.
33-
>
34-
> - Metastore is disabled in Synapse workspaces that have Managed Virtual Network with data exfiltration protection enabled. You can't use Spark SQL in these workspaces.
32+
> Resources in tenants other than the workspace's tenant must not have blocking firewall rules in place for the SQL pools to connect to them. Resources within the workspace’s managed virtual network, such as Spark clusters, can connect over managed private links to firewall-protected resources.
3533
> >
3634
3735
## Next Steps

0 commit comments

Comments
 (0)