Merge pull request #109872 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to master to sync with https://github.com/Microsoft/azure-docs (branch master)

Author: huypub

articles/active-directory-b2c/custom-policy-localization.md

@@ -17,7 +17,7 @@ ms.subservice: B2C
 
 [!INCLUDE [active-directory-b2c-advanced-audience-warning](../../includes/active-directory-b2c-advanced-audience-warning.md)]
 
-Language customization in Azure Active Directory B2C (Azure AD B2C) allows you to accommodate different languages to suit your customer' needs. Microsoft provides the translations for 36 languages, but you can also provide your own translations for any language. Even if your experience is provided for only a single language, you can customize any text on the pages. 
+Language customization in Azure Active Directory B2C (Azure AD B2C) allows you to accommodate different languages to suit your customer' needs. Microsoft provides the translations for [36 languages](https://docs.microsoft.com/azure/active-directory-b2c/user-flow-language-customization#supported-languages), but you can also provide your own translations for any language. Even if your experience is provided for only a single language, you can customize any text on the pages. 
 
 This article shows you how to support multiple locales or languages in the policy for user journeys. Localization requires three steps: set-up the explicit list of supported languages, provide language-specific strings and collections, and edit the [content definition](contentdefinitions.md) for the page. 
 

articles/application-gateway/self-signed-certificates.md

@@ -257,11 +257,13 @@ Add-AzApplicationGatewayRequestRoutingRule `
 
 Set-AzApplicationGateway -ApplicationGateway $gw 
 ```
+
 ### Verify the application gateway backend health
 
 1. Click the **Backend Health** view of your application gateway to check if the probe is healthy.
-1.    You should see that the Status is **Healthy** for the HTTPS probe.
-      ![HTTPS probe](media/self-signed-certificates/https-probe.png)
+1. You should see that the Status is **Healthy** for the HTTPS probe.
+
+![HTTPS probe](media/self-signed-certificates/https-probe.png)
 
 ## Next steps
 

articles/asc-for-iot/how-to-deploy-edge.md

@@ -93,7 +93,7 @@ Complete each step to complete your IoT Edge deployment for Azure Security Cente
 1. On the **Module Twin Settings** tab, add the following configuration:
 
     ``` json
-      "ms_iotn:urn_azureiot_Security_SecurityAgentConfiguration":{}
+      "ms_iotn:urn_azureiot_Security_SecurityAgentConfiguration"
     ```
 
 1. Select **Update**.

articles/azure-signalr/signalr-quickstart-rest-api.md

@@ -125,10 +125,17 @@ API | `1.0-preview` | `1.0`
 [Broadcast to all](#broadcast) | **✓** | **✓**
 [Broadcast to a group](#broadcast-group) | **✓** | **✓**
 Broadcast to some groups | **✓** (Deprecated) | `N / A`
-[Send to specific users](#send-user) | **✓** | **✓**
+[Send to a user](#send-user) | **✓** | **✓**
 Send to some users | **✓** (Deprecated) | `N / A`
 [Adding a user to a group](#add-user-to-group) | `N / A` | **✓**
 [Removing a user from a group](#remove-user-from-group) | `N / A` | **✓**
+[Check user existence](#check-user-existence) | `N / A` | **✓**
+[Remove a user from all groups](#remove-user-from-all-groups) | `N / A` | **✓**
+[Send to a connection](#send-connection) | `N / A` | **✓**
+[Add a connection to a group](#add-connection-to-group) | `N / A` | **✓**
+[Remove a connection from a group](#remove-connection-from-group) | `N / A` | **✓**
+[Close a client connection](#close-connection) | `N / A` | **✓**
+[Service Health](#service-health) | `N / A` | **✓**
 
 <a name="broadcast"> </a>
 ### Broadcast to everyone
@@ -147,7 +154,7 @@ Version | API HTTP Method | Request URL | Request body
 `1.0` | `POST` | `https://<instance-name>.service.signalr.net/api/v1/hubs/<hub-name>/groups/<group-name>` | Same as above
 
 <a name="send-user"> </a>
-### Sending to specific users
+### Sending to a user
 
 Version | API HTTP Method | Request URL | Request body
 --- | --- | --- | ---
@@ -159,14 +166,77 @@ Version | API HTTP Method | Request URL | Request body
 
 Version | API HTTP Method | Request URL
 --- | --- | ---
-`1.0` | `PUT` | `https://<instance-name>.service.signalr.net/api/v1/hubs/<hub-name>/groups/<group-name>/users/<userid>`
+`1.0` | `PUT` | `https://<instance-name>.service.signalr.net/api/v1/hubs/<hub-name>/groups/<group-name>/users/<user-id>`
 
 <a name="remove-user-from-group"> </a>
 ### Removing a user from a group
 
 Version | API HTTP Method | Request URL
 --- | --- | ---
-`1.0` | `DELETE` | `https://<instance-name>.service.signalr.net/api/v1/hubs/<hub-name>/groups/<group-name>/users/<userid>`
+`1.0` | `DELETE` | `https://<instance-name>.service.signalr.net/api/v1/hubs/<hub-name>/groups/<group-name>/users/<user-id>`
+
+<a name="check-user-existence"> </a>
+### Check user existence in a group
+
+API Version | API HTTP Method | Request URL
+---|---|---
+`1.0` | `GET` | `https://<instance-name>.service.signalr.net/api/v1/hubs/<hub-name>/users/<user-id>/groups/<group-name>`
+`1.0` | `GET` | `https://<instance-name>.service.signalr.net/api/v1/hubs/<hub-name>/groups/<group-name>/users/<user-id>` 
+
+Response Status Code | Description
+---|---
+`200` | User exists
+`404` | User not exists
+
+<a name="remove-user-from-all-groups"> </a>
+### Remove a user from all groups
+
+API Version | API HTTP Method | Request URL
+---|---|---
+`1.0` | `DELETE` | `https://<instance-name>.service.signalr.net/api/v1/hubs/<hub-name>/users/<user-id>/groups`
+
+<a name="send-connection"> </a>
+### Send message to a connection
+
+API Version | API HTTP Method | Request URL | Request Body
+---|---|---|---
+`1.0` | `POST` | `https://<instance-name>.service.signalr.net/api/v1/hubs/<hub-name>/connections/<connection-id>` | `{ "target":"<method-name>", "arguments":[ ... ] }`
+
+<a name="add-connection-to-group"> </a>
+### Add a connection to a group
+
+API Version | API HTTP Method | Request URL
+---|---|---
+`1.0` | `PUT` | `https://<instance-name>.service.signalr.net/api/v1/hubs/<hub-name>/groups/<group-name>/connections/<connection-id>`
+`1.0` | `PUT` | `https://<instance-name>.service.signalr.net/api/v1/hubs/<hub-name>/connections/<connection-id>/groups/<group-name>`
+
+<a name="remove-connection-from-group"> </a>
+### Remove a connection from a group
+
+API Version | API HTTP Method | Request URL
+---|---|---
+`1.0` | `DELETE` | `https://<instance-name>.service.signalr.net/api/v1/hubs/<hub-name>/groups/<group-name>/connections/<connection-id>`
+`1.0` | `DELETE` | `https://<instance-name>.service.signalr.net/api/v1/hubs/<hub-name>/connections/<connection-id>/groups/<group-name>`
+
+<a name="close-connection"> </a>
+### Close a client connection
+
+API Version | API HTTP Method | Request URL
+---|---|---
+`1.0` | `DELETE` | `https://<instance-name>.service.signalr.net/api/v1/hubs/<hub-name>/connections/<connection-id>`
+`1.0` | `DELETE` | `https://<instance-name>.service.signalr.net/api/v1/hubs/<hub-name>/connections/<connection-id>?reason=<close-reason>`
+
+<a name="service-health"> </a>
+### Service Health
+
+API Version | API HTTP Method | Request URL
+---|---|---                             
+`1.0` | `GET` | `https://<instance-name>.service.signalr.net/api/v1/health`
+
+Response Status Code | Description
+---|---
+`200` | Service Good
+`503` | Service Unavailable
 
 [!INCLUDE [Cleanup](includes/signalr-quickstart-cleanup.md)]
 

articles/data-factory/data-flow-expression-functions.md

@@ -115,6 +115,12 @@ Returns the first not null value from a set of inputs. All inputs should be of t
 * ``coalesce(10, 20) -> 10``
 * ``coalesce(toString(null), toString(null), 'dumbo', 'bo', 'go') -> 'dumbo'``
 ___
+### <code>columnNames</code>
+<code><b>columnNames(<i>&lt;value1&gt;</i> : string) => array</b></code><br/><br/>
+Gets all output columns for a stream. You can pass a optional stream name as the second argument.
+* ``columnNames()``
+* ``columnNames('DeriveStream')``
+___
 ### <code>compare</code>
 <code><b>compare(<i>&lt;value1&gt;</i> : any, <i>&lt;value2&gt;</i> : any) => integer</b></code><br/><br/>
 Compares two values of the same type. Returns negative integer if value1 < value2, 0 if value1 == value2, positive value if value1 > value2

articles/event-hubs/get-started-dotnet-standard-send-v2.md

@@ -202,7 +202,7 @@ In this quickstart, you use Azure Storage as the checkpoint store. Follow these
         static Task ProcessEventHandler(ProcessEventArgs eventArgs)
         { 
             // Write the body of the event to the console window
-            Console.WriteLine("\tRecevied event: {0}", Encoding.UTF8.GetString(eventArgs.Data.Body.ToArray())); 
+            Console.WriteLine("\tReceived event: {0}", Encoding.UTF8.GetString(eventArgs.Data.Body.ToArray())); 
             return Task.CompletedTask; 
         }
 

articles/iot-accelerators/iot-accelerators-remote-monitoring-sample-walkthrough.md

@@ -121,9 +121,6 @@ The ASA jobs deliver the telemetry from the connected devices to Time Series Ins
 
 [Azure Time Series Insights](https://docs.microsoft.com/azure/time-series-insights/) stores the telemetry from the devices connected to the solution accelerator. It also enables visualizing and querying device telemetry in the solution web UI.
 
-> [!NOTE]
-> Time Series Insights is not currently available in the Azure China cloud. New Remote Monitoring solution accelerator deployments in the Azure China cloud use Cosmos DB for all storage.
-
 ### Configuration microservice
 
 The [configuration microservice](https://github.com/Azure/remote-monitoring-services-dotnet/tree/master/config) provides a RESTful endpoint for CRUD operations on device groups, solution settings, and user-settings in the solution accelerator. It works with the storage adapter microservice to persist the configuration data.

articles/marketplace/marketplace-saas-applications-technical-publishing-guide.md

@@ -20,8 +20,8 @@ SaaS applications are available in both Azure Storefronts The following table de
 
 | Storefront option | Listing | Trial/Transact |  
 | --- | --- | --- |  
-| AppSource | Yes (Contact Me) | Yes (PowerBI/Dynamics) |
-| Azure marketplace | No | Yes (SaaS Apps) |   
+| AppSource | Yes | Yes |
+| Azure marketplace | No | Yes |   
 
 **List:**  The Listing publishing option consists of a Contact Me offer type and is used when a Trial- or Transaction-level participation is not feasible. The benefit of this approach is that it enables publishers with a solution in-market to immediately begin receiving leads that can be turned into deals to increase your business.  
 **Trial/Transaction:**  The customer has the option to directly buy or request a trial for your solution. Providing a Trial experience increases the engagement level offered to customers and enables customers to explore your solution before buying. With a Trial experience, you will have better chances of promotion in the storefronts, and you should expect more and richer leads from customer engagements. Trials must include free support at least for the duration of the trial period.  

articles/storsimple/storsimple-ova-best-practices.md

@@ -157,8 +157,8 @@ Keep in mind the following best practices when provisioning shares or volumes on
 
 * The file sizes relative to the provisioned size of a tiered share can impact the tiering performance. Working with large files could result in a slow tier out. When working with large files, we recommend that the largest file is smaller than 3% of the share size.
 * A maximum of 16 volumes/shares can be created on the virtual array. For the size limits of the locally pinned and tiered volumes/shares, always refer to the [StorSimple Virtual Array limits](storsimple-ova-limits.md).
-* When creating a volume, factor in the expected data consumption as well as future growth. The volume cannot be expanded later.
-* Once the volume has been created, you cannot shrink the size of the volume on StorSimple.
+* When creating a volume, factor in the expected data consumption as well as future growth. The volume or share cannot be expanded later.
+* Once the volume/share has been created, you cannot shrink the size of the volume/share on StorSimple.
 * When writing to a tiered volume on StorSimple, when the volume data reaches a certain threshold (relative to the local space reserved for the volume), the IO is throttled. Continuing to write to this volume slows down the IO significantly. Though you can write to a tiered volume beyond its provisioned capacity (we do not actively stop the user from writing beyond the provisioned capacity), you see an alert notification to the effect that you have oversubscribed. Once you see the alert, it is imperative that you take remedial measures such as delete the volume data (volume expansion is currently not supported).
 * For disaster recovery use cases, as the number of allowable shares/volumes is 16 and the maximum number of shares/volumes that can be processed in parallel is also 16, the number of shares/volumes does not have a bearing on your RPO and RTOs.