title: Enable-PSRemoting command failing in powershell, Azure VM
body: <p>I tried the <code>Enable-PSRemoting</code> in powershell, Windows 10 Pro, configured in Azure VM.
  But the command fails with the following error :</p>
  <pre><code>WinRM has been updated to receive requests.
  WinRM service type changed successfully.
  WinRM service started.
  
  Set-WSManQuickConfig : &lt;f:WSManFault xmlns:f=&quot;http://schemas.microsoft.com/wbem/wsman/1/wsmanfault&quot; Code=&quot;2150859113&quot;
  Machine=&quot;localhost&quot;&gt;&lt;f:Message&gt;&lt;f:ProviderFault provider=&quot;Config provider&quot;
  path=&quot;%systemroot%\system32\WsmSvc.dll&quot;&gt;&lt;f:WSManFault xmlns:f=&quot;http://schemas.microsoft.com/wbem/wsman/1/wsmanfault&quot;
  Code=&quot;2150859113&quot; Machine=&quot;Roshin&quot;&gt;&lt;f:Message&gt;WinRM firewall exception will not work since one of the network
  connection types on this machine is set to Public. Change the network connection type to either Domain or Private and
  try again. &lt;/f:Message&gt;&lt;/f:WSManFault&gt;&lt;/f:ProviderFault&gt;&lt;/f:Message&gt;&lt;/f:WSManFault&gt;
  At line:116 char:17
  +                 Set-WSManQuickConfig -force
  +                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
      + CategoryInfo          : InvalidOperation: (:) [Set-WSManQuickConfig], InvalidOperationException
      + FullyQualifiedErrorId : WsManError,Microsoft.WSMan.Management.SetWSManQuickConfigCommand
  </code></pre>
  <p>Can someone help to mitigate this?</p>