Merge pull request #87646 from MicrosoftDocs/repo_sync_working_branch

huypub · web-flow · commit 32a43d3053ef · 2019-09-06T09:46:59.000-07:00
Confirm merge from repo_sync_working_branch to master to sync with https://github.com/Microsoft/azure-docs (branch master)
diff --git a/articles/active-directory/authentication/howto-sspr-deployment.md b/articles/active-directory/authentication/howto-sspr-deployment.md
@@ -34,7 +34,7 @@ Before deploying SSPR, organizations may want to determine how many password res
 
 ## Licensing considerations
 
-Azure Active Directory is license per-user meaning each user has to have an appropriate license for the features they utilize.
+Azure Active Directory is licensed per-user meaning each user has to have an appropriate license for the features they utilize.
 
 More information about licensing can be found on the [Azure Active Directory pricing page](https://azure.microsoft.com/pricing/details/active-directory/)
 
diff --git a/articles/azure-monitor/app/ip-addresses.md b/articles/azure-monitor/app/ip-addresses.md
@@ -31,7 +31,7 @@ You need to open some outgoing ports in your server's firewall to allow the Appl
 
 | Purpose | URL | IP | Ports |
 | --- | --- | --- | --- |
-| Telemetry |dc.services.visualstudio.com<br/>dc.applicationinsights.microsoft.com |40.114.241.141<br/>104.45.136.42<br/>40.84.189.107<br/>168.63.242.221<br/>52.167.221.184<br/>52.169.64.244<br/>40.85.218.175<br/>104.211.92.54<br/>52.175.198.74<br/>51.140.6.23<br/>40.71.12.231<br/>13.69.65.22<br/>13.78.108.165<br/>13.70.72.233<br/>20.44.8.7<br/>13.86.218.248<br/>40.79.138.41<br/>52.231.18.241<br/>13.75.38.7<br/>102.133.162.117<br/>40.73.171.20<br/>102.133.155.50<br/>52.162.110.67<br/>191.233.203.238 | 443 |
+| Telemetry |dc.services.visualstudio.com<br/>dc.applicationinsights.microsoft.com |40.114.241.141<br/>104.45.136.42<br/>40.84.189.107<br/>168.63.242.221<br/>52.167.221.184<br/>52.169.64.244<br/>40.85.218.175<br/>104.211.92.54<br/>52.175.198.74<br/>51.140.6.23<br/>40.71.12.231<br/>13.69.65.22<br/>13.78.108.165<br/>13.70.72.233<br/>20.44.8.7<br/>13.86.218.248<br/>40.79.138.41<br/>52.231.18.241<br/>13.75.38.7<br/>102.133.162.117<br/>40.73.171.20<br/>102.133.155.50<br/>52.162.110.67<br/>191.233.203.248 | 443 |
 | Live Metrics Stream |rt.services.visualstudio.com<br/>rt.applicationinsights.microsoft.com |23.96.28.38<br/>13.92.40.198 |443 |
 
 ## Status Monitor
diff --git a/articles/azure-monitor/insights/solutions-resources-searches-alerts.md b/articles/azure-monitor/insights/solutions-resources-searches-alerts.md
@@ -166,28 +166,28 @@ The properties for Alert action resources are described in the following tables.
 
 | Element name | Required | Description |
 |:--|:--|:--|
-| Type | Yes | Type of the action.  This is **Alert** for alert actions. |
-| Name | Yes | Display name for the alert.  This is the name that's displayed in the console for the alert rule. |
-| Description | No | Optional description of the alert. |
-| Severity | Yes | Severity of the alert record from the following values:<br><br> **critical**<br>**warning**<br>**informational**
+| `Type` | Yes | Type of the action.  This is **Alert** for alert actions. |
+| `Name` | Yes | Display name for the alert.  This is the name that's displayed in the console for the alert rule. |
+| `Description` | No | Optional description of the alert. |
+| `Severity` | Yes | Severity of the alert record from the following values:<br><br> **critical**<br>**warning**<br>**informational**
 
 
 #### Threshold
 This section is required. It defines the properties for the alert threshold.
 
 | Element name | Required | Description |
 |:--|:--|:--|
-| Operator | Yes | Operator for the comparison from the following values:<br><br>**gt = greater than<br>lt = less than** |
-| Value | Yes | The value to compare the results. |
+| `Operator` | Yes | Operator for the comparison from the following values:<br><br>**gt = greater than<br>lt = less than** |
+| `Value` | Yes | The value to compare the results. |
 
 ##### MetricsTrigger
 This section is optional. Include it for a metric measurement alert.
 
 | Element name | Required | Description |
 |:--|:--|:--|
-| TriggerCondition | Yes | Specifies whether the threshold is for total number of breaches or consecutive breaches from the following values:<br><br>**Total<br>Consecutive** |
-| Operator | Yes | Operator for the comparison from the following values:<br><br>**gt = greater than<br>lt = less than** |
-| Value | Yes | Number of the times the criteria must be met to trigger the alert. |
+| `TriggerCondition` | Yes | Specifies whether the threshold is for total number of breaches or consecutive breaches from the following values:<br><br>**Total<br>Consecutive** |
+| `Operator` | Yes | Operator for the comparison from the following values:<br><br>**gt = greater than<br>lt = less than** |
+| `Value` | Yes | Number of the times the criteria must be met to trigger the alert. |
 
 
 #### Throttling
diff --git a/articles/cognitive-services/Speech-Service/how-to-custom-speech-human-labeled-transcriptions.md b/articles/cognitive-services/Speech-Service/how-to-custom-speech-human-labeled-transcriptions.md
@@ -69,7 +69,7 @@ Here are a few examples of normalization automatically performed on the transcri
 | Go get -em! | go get em |
 | I'm double-jointed | I'm double jointed |
 | 104 Elm Street | one oh four Elm street |
-| Tune to 102.7 | tune to one oh two seven |
+| Tune to 102.7 | tune to one oh two point seven |
 | Pi is about 3.14 | pi is about three point one four |
 It costs $3.14| it costs three fourteen |
 
diff --git a/articles/dms/known-issues-azure-postgresql-online.md b/articles/dms/known-issues-azure-postgresql-online.md
@@ -85,6 +85,8 @@ Known issues and limitations associated with online migrations from PostgreSQL t
 
     **Workaround**: Temporarily set a primary key for the table for migration to continue. You can remove the primary key after data migration is complete.
 
+- **Limitation**: JSONB datatype not supported for migration.
+
 ## LOB limitations
 
 Large Object (LOB) columns are columns that can grow large. For PostgreSQL, examples of LOB data types include XML, JSON, IMAGE, TEXT, etc.
diff --git a/articles/sql-database/sql-database-managed-instance-transact-sql-information.md b/articles/sql-database/sql-database-managed-instance-transact-sql-information.md
@@ -334,7 +334,7 @@ A managed instance can't access file shares and Windows folders, so the followin
 - `ALTER ASSEMBLY` can't reference files. See [ALTER ASSEMBLY](https://docs.microsoft.com/sql/t-sql/statements/alter-assembly-transact-sql).
 
 ### Database Mail (db_mail)
- - `sp_send_dbmail` cannot send atachments using @file_attachments parameter. Local file system and extental shares or Azure blob Storage are not accessible form this procedure.
+ - `sp_send_dbmail` cannot send attachments using @file_attachments parameter. Local file system and extental shares or Azure blob Storage are not accessible form this procedure.
  - See the known issues related to `@query` parameter and authentication.
  
 ### DBCC
diff --git a/articles/virtual-machines/windows/sql/virtual-machines-windows-sql-register-with-resource-provider.md b/articles/virtual-machines/windows/sql/virtual-machines-windows-sql-register-with-resource-provider.md
@@ -333,15 +333,15 @@ Yes. Upgrading the manageability mode from lightweight to full is supported via
 
 No. Downgrading the SQL Server IaaS extension manageability mode is not supported. The manageability mode can't be downgraded from full mode to lightweight or no-agent mode, and it can't be downgraded from lightweight mode to no-agent mode. 
 
-To change the manageability mode from full manageability, remove the SQL Server IaaS extension. Then, drop the Micorsoft.SqlVirtualMachine resource and re-register the SQL Server VM with the SQL VM resource provider.
+To change the manageability mode from full manageability, remove the SQL Server IaaS extension. Then, drop the Microsoft.SqlVirtualMachine resource and re-register the SQL Server VM with the SQL VM resource provider.
 
 **Can I register with the SQL VM resource provider from the Azure portal?**
 
 No. Registering with the SQL VM resource provider is not available in the Azure portal. Registering with the SQL VM resource provider in full manageability mode is supported with the Azure CLI or PowerShell. Registering with the SQL VM resource provider in lightweight or no-agent manageability mode is supported only by Azure PowerShell APIs.
 
 **Can I register a VM with the SQL VM resource provider before SQL Server is installed?**
 
-No. A VM should have at least one SQL Server instance to successfully register with the SQL VM resource provider. If there is no SQL Server instance on the VM, the new Micosoft.SqlVirtualMachine resource will be in a failed state.
+No. A VM should have at least one SQL Server instance to successfully register with the SQL VM resource provider. If there is no SQL Server instance on the VM, the new Microsoft.SqlVirtualMachine resource will be in a failed state.
 
 **Can I register a VM with the SQL VM resource provider if there are multiple SQL Server instances?**
 
@@ -362,4 +362,4 @@ For more information, see the following articles:
 * [Overview of SQL Server on a Windows VM](virtual-machines-windows-sql-server-iaas-overview.md)
 * [FAQ for SQL Server on a Windows VM](virtual-machines-windows-sql-server-iaas-faq.md)
 * [Pricing guidance for SQL Server on a Windows VM](virtual-machines-windows-sql-server-pricing-guidance.md)
-* [Release notes for SQL Server on a Windows VM](virtual-machines-windows-sql-server-iaas-release-notes.md)
+* [Release notes for SQL Server on a Windows VM](virtual-machines-windows-sql-server-iaas-release-notes.md)
