Merge pull request #5750 from Microsoft/FromPublicRepo

From public repo

Author: v-anpasi

articles/active-directory/active-directory-conditional-access-automatic-device-registration-faq.md

@@ -53,15 +53,15 @@ For more details, see the [Get-MsolDevice](https://docs.microsoft.com/en-us/powe
 **Q: Why is a device I have deleted in the Azure portal or using Windows PowerShell still listed as registered?**
 
 **A:** This is by design. The device will not have access to resources in the cloud. 
-If you want to re-register the device, a manual action needs to be taken on the device. 
+If you want to remove the device and register again, a manual action must be to be taken on the device. 
 
 For Windows 10 and Windows Server 2016 that are on-premises AD domain-joined:
 
 1.	Open the command prompt as an administrator.
 
-2.	Type **dsregcmd.exe /leave**.
+2.	Type **dsregcmd.exe /debug /leave**
 
-3.	Type **dsregcmd.exe**.
+3.	**Sign Out and Sign In to trigger the scheduled task that registers the device again.** 
 
 For other Windows platforms that are on-premises AD domain-joined:
 

articles/app-service-web/app-service-web-get-started.md

@@ -54,7 +54,7 @@ You can complete the task using one of the following CLI versions:
 ## Deploy a web app
 Let's deploy a web app to Azure App Service.
 
-1. Open a new Windows command prompt, PowerShell window, Linux shell, or OS X terminal. Run `git --version` and `azure --version` to verify that Git and Azure CLI
+1. Open a new Windows command prompt, PowerShell window, Linux shell, or OS X terminal. Run `git --version` and `az --version` to verify that Git and Azure CLI
    are installed on your machine.
 
     ![Test installation of CLI tools for your first web app in Azure](./media/app-service-web-get-started/1-test-tools-2.0.png)

articles/application-insights/app-insights-powershell-alerts.md

@@ -105,13 +105,13 @@ The same rule can be used for the metric reported by using the [measurement para
 | `clientPerformance.total.value` |Browser page load time |Time from user request until DOM, stylesheets, scripts and images are loaded. |
 | `performanceCounter.available_bytes.value` |Available memory |Physical memory immediately available for a process or for system use. |
 | `performanceCounter.io_data_bytes_per_sec.value` |Process IO Rate |Total bytes per second read and written to files, network and devices. |
-| `performanceCounter.number_of_exceps_thrown_per_sec` |exception rate |Exceptions thrown per second. |
+| `performanceCounter.number_of_exceps_thrown_per_sec.value` |exception rate |Exceptions thrown per second. |
 | `performanceCounter.percentage_processor_time.value` |Process CPU |The percentage of elapsed time of all process threads used by the processor to execution instructions for the applications process. |
 | `performanceCounter.percentage_processor_total.value` |Processor time |The percentage of time that the processor spends in non-Idle threads. |
 | `performanceCounter.process_private_bytes.value` |Process private bytes |Memory exclusively assigned to the monitored application's processes. |
 | `performanceCounter.request_execution_time.value` |ASP.NET request execution time |Execution time of the most recent request. |
 | `performanceCounter.requests_in_application_queue.value` |ASP.NET requests in execution queue |Length of the application request queue. |
-| `performanceCounter.requests_per_sec` |ASP.NET request rate |Rate of all requests to the application per second from ASP.NET. |
+| `performanceCounter.requests_per_sec.value` |ASP.NET request rate |Rate of all requests to the application per second from ASP.NET. |
 | `remoteDependencyFailed.durationMetric.count` |Dependency failures |Count of failed calls made by the server application to external resources. |
 | `request.duration` |Server response time |Time between receiving an HTTP request and finishing sending the response. |
 | `request.rate` |Request rate |Rate of all requests to the application per second. |

articles/container-service/container-service-connect.md

@@ -77,7 +77,7 @@ This command downloads the cluster credentials to `$HOME/.kube/config`, where `k
 Alternatively, you can use `scp` to securely copy the file from `$HOME/.kube/config` on the master VM to your local machine. For example:
 
 ```console
-mkdir $HOME/.kube/config
+mkdir $HOME/.kube
 scp azureuser@<master-dns-name>:.kube/config $HOME/.kube/config
 ```
 

articles/iot-hub/iot-hub-device-sdk-c-serializer.md

@@ -523,6 +523,13 @@ For example, to invoke **SetAirResistance** you can send this message to a devic
 
 The action name must exactly match an action defined in your model. The parameter names must match as well. Also note case sensitivity. **Name** and **Parameters** are always uppercase. Make sure to match the case of your action name and parameters in your model. In this example, the action name is "SetAirResistance" and not "setairresistance".
 
+The two other actions **TurnFanOn** and **TurnFanOff** can be invoked by sending these messages to a device:
+
+```
+{"Name" : "TurnFanOn", "Parameters" : {}}
+{"Name" : "TurnFanOff", "Parameters" : {}}
+```
+
 This section described everything you need to know when sending events and receiving messages with the **serializer** library. Before moving on, let's cover some parameters you can configure that control how large your model is.
 
 ## Macro configuration