Merge pull request #114985 from MicrosoftDocs/master

10am Publish

Author: SyntaxC4

articles/databox/data-box-deploy-copy-data.md

@@ -22,7 +22,7 @@ ms.localizationpriority: high
 
 ::: zone target="chromeless"
 
-# Copy data to Azure Data Box
+## Copy data to Azure Data Box
 
 ::: zone-end
 

articles/databox/data-box-deploy-picked-up.md

@@ -22,7 +22,7 @@ ms.localizationpriority: high
 
 ::: zone target="chromeless"
 
-# Return Data Box and verify data upload to Azure
+## Return Data Box and verify data upload to Azure
 
 ::: zone-end
 

articles/databox/data-box-deploy-set-up.md

@@ -22,7 +22,7 @@ ms.localizationpriority: high
 
 ::: zone target="chromeless"
 
-# Cable and connect to your device
+## Cable and connect to your device
 
 ::: zone-end
 

articles/databox/data-box-heavy-deploy-copy-data.md

@@ -20,7 +20,7 @@ ms.localizationpriority: high
 
 ::: zone target = "chromeless"
 
-# Copy data to Azure Data Box Heavy
+## Copy data to Azure Data Box Heavy
 
 ::: zone-end
 

articles/databox/data-box-heavy-deploy-picked-up.md

@@ -22,7 +22,7 @@ ms.localizationpriority: high
 
 ::: zone target = "chromeless"
 
-# Return Azure Data Box Heavy and verify data upload to Azure
+## Return Azure Data Box Heavy and verify data upload to Azure
 
 ::: zone-end
 

articles/databox/data-box-heavy-deploy-set-up.md

@@ -21,7 +21,7 @@ ms.localizationpriority: high
 
 ::: zone target = "chromeless"
 
-# Get started with Azure Data Box Heavy
+## Get started with Azure Data Box Heavy
 
 ::: zone-end
 

articles/databox/data-box-heavy-quickstart-portal.md

@@ -71,7 +71,7 @@ Once the order is created, the device is prepared for shipment.
 
 ::: zone target = "chromeless"
 
-# Cable and connect to your device
+## Cable and connect to your device
 
 After you have reviewed the prerequisites, you'll cable and connect to your device.
 

articles/security-center/TOC.yml

@@ -12,6 +12,8 @@
       href: security-center-services.md
     - name: Feature coverage for Azure PaaS resources
       href: features-paas.md
+  - name: What's new in Security Center?
+    href: release-notes.md
   - name: Security recommendations
     href: recommendations-reference.md
   - name: Security alerts and the intent kill chain
@@ -194,7 +196,9 @@
       href: faq-vms.md      
     - name: Existing users of Azure Log Analytics
       href: faq-azure-monitor-logs.md      
-  - name: Release notes
+  - name: Archive of what's new in Security Center?
+    href: release-notes-archive.md
+  - name: Azure roadmap blog
     href: https://azure.microsoft.com/updates/?product=security-center
   - name: Features and API retirement (July 2019)
     href: security-center-features-retirement-july2019.md

articles/security-center/recommendations-reference.md

@@ -36,7 +36,7 @@ Your Secure Score is based on the number of Security Center recommendations you'
 |**Function App should only be accessible over HTTPS**|Enable "HTTPS only" access for function apps. Use of HTTPS ensures server/service authentication and protects data in transit from network layer eavesdropping attacks.<br>(Related policy: Function App should only be accessible over HTTPS)|Medium|**Y**|Function app|
 |**Internet-facing virtual machines should be protected with Network Security Groups**|Enable Network Security Groups to control network access of your virtual machines.<br>(Related policy: Internet-facing virtual machines should be protected with Network Security Groups)|High/ Medium|N|Virtual machine|
 |**IP forwarding on your virtual machine should be disabled**|Disable IP forwarding. When IP forwarding is enabled on a virtual machine's NIC, the machine can receive traffic addressed to other destinations. IP forwarding is rarely required (for example, when using the VM as a network virtual appliance), and therefore, this should be reviewed by the network security team.<br>(Related policy: [Preview]: IP Forwarding on your virtual machine should be disabled)|Medium|N|Virtual machine|
-|**Just-in-time network access control should be applied on virtual machines**|Apply just-in-time (JIT) virtual machine (VM) access control to permanently lock down access to selected ports, and enable authorized users to open them, via JIT, for a limited amount of time only.<br>(Related policy: Just-In-Time network access control should be applied on virtual machines)|High|N|Virtual machine|
+|**Management ports of virtual machines should be protected with just-in-time network access control**|Apply just-in-time (JIT) virtual machine (VM) access control to permanently lock down access to selected ports, and enable authorized users to open them, via JIT, for a limited amount of time only.<br>(Related policy: Management ports of virtual machines should be protected with just-in-time network access control)|High|N|Virtual machine|
 |**Management ports should be closed on your virtual machines**|Harden the network security group of your virtual machines to restrict access to management ports.<br>(Related policy: Management ports should be closed on your virtual machines)|High|N|Virtual machine|
 |**Secure transfer to storage accounts should be enabled**|Enable secure transfer to storage accounts. Secure transfer is an option that forces your storage account to accept requests only from secure connections (HTTPS). Use of HTTPS ensures authentication between the server and the service and protects data in transit from network layer attacks, such as man-in-the-middle, eavesdropping, and session-hijacking.<br>(Related policy: Secure transfer to storage accounts should be enabled)|High|**Y**|Storage account|
 |**Subnets should be associated with a Network Security Group**|Enable network security groups to control network access of resources deployed in your subnets.<br>(Related policy: Subnets should be associated with a Network Security Group.<br>This policy is disabled by default)|High/ Medium|N|Subnet|