diff --git a/azure-mgmt-sql/azure/mgmt/sql/models/database_blob_auditing_policy.py b/azure-mgmt-sql/azure/mgmt/sql/models/database_blob_auditing_policy.py
index 57e85a7ffeef..6db06ede30ad 100644
--- a/azure-mgmt-sql/azure/mgmt/sql/models/database_blob_auditing_policy.py
+++ b/azure-mgmt-sql/azure/mgmt/sql/models/database_blob_auditing_policy.py
@@ -92,10 +92,10 @@ class DatabaseBlobAuditingPolicy(ProxyResource):
      RECEIVE
      REFERENCES
      The general form for defining an action to be audited is:
-     <action> ON <object> BY <principal>
+     {action} ON {object} BY {principal}
      Note that <object> in the above format can refer to an object like a
      table, view, or stored procedure, or an entire database or schema. For the
-     latter cases, the forms DATABASE::<db_name> and SCHEMA::<schema_name> are
+     latter cases, the forms DATABASE::{db_name} and SCHEMA::{schema_name} are
      used, respectively.
      For example:
      SELECT on dbo.myTable by public
@@ -118,10 +118,10 @@ class DatabaseBlobAuditingPolicy(ProxyResource):
      'SQLSecurityAuditEvents' diagnostic logs category on the database should
      be also created.
      Note that for server level audit you should use the 'master' database as
-     <databaseName>.
+     {databaseName}.
      Diagnostic Settings URI format:
      PUT
-     https://management.azure.com/subscriptions/<subscriptionId>/resourceGroups/<resourceGroup>/providers/Microsoft.Sql/servers/<serverName>/databases/<databaseName>/providers/microsoft.insights/diagnosticSettings/<settingsName>?api-version=2017-05-01-preview
+     https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/providers/microsoft.insights/diagnosticSettings/{settingsName}?api-version=2017-05-01-preview
      For more information, see [Diagnostic Settings REST
      API](https://go.microsoft.com/fwlink/?linkid=2033207)
      or [Diagnostic Settings
diff --git a/azure-mgmt-sql/azure/mgmt/sql/models/database_blob_auditing_policy_py3.py b/azure-mgmt-sql/azure/mgmt/sql/models/database_blob_auditing_policy_py3.py
index ab7e08965ed6..2acc43dae952 100644
--- a/azure-mgmt-sql/azure/mgmt/sql/models/database_blob_auditing_policy_py3.py
+++ b/azure-mgmt-sql/azure/mgmt/sql/models/database_blob_auditing_policy_py3.py
@@ -92,10 +92,10 @@ class DatabaseBlobAuditingPolicy(ProxyResource):
      RECEIVE
      REFERENCES
      The general form for defining an action to be audited is:
-     <action> ON <object> BY <principal>
+     {action} ON {object} BY {principal}
      Note that <object> in the above format can refer to an object like a
      table, view, or stored procedure, or an entire database or schema. For the
-     latter cases, the forms DATABASE::<db_name> and SCHEMA::<schema_name> are
+     latter cases, the forms DATABASE::{db_name} and SCHEMA::{schema_name} are
      used, respectively.
      For example:
      SELECT on dbo.myTable by public
@@ -118,10 +118,10 @@ class DatabaseBlobAuditingPolicy(ProxyResource):
      'SQLSecurityAuditEvents' diagnostic logs category on the database should
      be also created.
      Note that for server level audit you should use the 'master' database as
-     <databaseName>.
+     {databaseName}.
      Diagnostic Settings URI format:
      PUT
-     https://management.azure.com/subscriptions/<subscriptionId>/resourceGroups/<resourceGroup>/providers/Microsoft.Sql/servers/<serverName>/databases/<databaseName>/providers/microsoft.insights/diagnosticSettings/<settingsName>?api-version=2017-05-01-preview
+     https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/providers/microsoft.insights/diagnosticSettings/{settingsName}?api-version=2017-05-01-preview
      For more information, see [Diagnostic Settings REST
      API](https://go.microsoft.com/fwlink/?linkid=2033207)
      or [Diagnostic Settings
diff --git a/azure-mgmt-sql/azure/mgmt/sql/models/extended_database_blob_auditing_policy.py b/azure-mgmt-sql/azure/mgmt/sql/models/extended_database_blob_auditing_policy.py
index a7b143ea8b15..48c324aa3153 100644
--- a/azure-mgmt-sql/azure/mgmt/sql/models/extended_database_blob_auditing_policy.py
+++ b/azure-mgmt-sql/azure/mgmt/sql/models/extended_database_blob_auditing_policy.py
@@ -93,10 +93,10 @@ class ExtendedDatabaseBlobAuditingPolicy(ProxyResource):
      RECEIVE
      REFERENCES
      The general form for defining an action to be audited is:
-     <action> ON <object> BY <principal>
+     {action} ON {object} BY {principal}
      Note that <object> in the above format can refer to an object like a
      table, view, or stored procedure, or an entire database or schema. For the
-     latter cases, the forms DATABASE::<db_name> and SCHEMA::<schema_name> are
+     latter cases, the forms DATABASE::{db_name} and SCHEMA::{schema_name} are
      used, respectively.
      For example:
      SELECT on dbo.myTable by public
@@ -119,10 +119,10 @@ class ExtendedDatabaseBlobAuditingPolicy(ProxyResource):
      'SQLSecurityAuditEvents' diagnostic logs category on the database should
      be also created.
      Note that for server level audit you should use the 'master' database as
-     <databaseName>.
+     {databaseName}.
      Diagnostic Settings URI format:
      PUT
-     https://management.azure.com/subscriptions/<subscriptionId>/resourceGroups/<resourceGroup>/providers/Microsoft.Sql/servers/<serverName>/databases/<databaseName>/providers/microsoft.insights/diagnosticSettings/<settingsName>?api-version=2017-05-01-preview
+     https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/providers/microsoft.insights/diagnosticSettings/{settingsName}?api-version=2017-05-01-preview
      For more information, see [Diagnostic Settings REST
      API](https://go.microsoft.com/fwlink/?linkid=2033207)
      or [Diagnostic Settings
diff --git a/azure-mgmt-sql/azure/mgmt/sql/models/extended_database_blob_auditing_policy_py3.py b/azure-mgmt-sql/azure/mgmt/sql/models/extended_database_blob_auditing_policy_py3.py
index 5a4c8f173611..9550f279968c 100644
--- a/azure-mgmt-sql/azure/mgmt/sql/models/extended_database_blob_auditing_policy_py3.py
+++ b/azure-mgmt-sql/azure/mgmt/sql/models/extended_database_blob_auditing_policy_py3.py
@@ -93,10 +93,10 @@ class ExtendedDatabaseBlobAuditingPolicy(ProxyResource):
      RECEIVE
      REFERENCES
      The general form for defining an action to be audited is:
-     <action> ON <object> BY <principal>
+     {action} ON {object} BY {principal}
      Note that <object> in the above format can refer to an object like a
      table, view, or stored procedure, or an entire database or schema. For the
-     latter cases, the forms DATABASE::<db_name> and SCHEMA::<schema_name> are
+     latter cases, the forms DATABASE::{db_name} and SCHEMA::{schema_name} are
      used, respectively.
      For example:
      SELECT on dbo.myTable by public
@@ -119,10 +119,10 @@ class ExtendedDatabaseBlobAuditingPolicy(ProxyResource):
      'SQLSecurityAuditEvents' diagnostic logs category on the database should
      be also created.
      Note that for server level audit you should use the 'master' database as
-     <databaseName>.
+     {databaseName}.
      Diagnostic Settings URI format:
      PUT
-     https://management.azure.com/subscriptions/<subscriptionId>/resourceGroups/<resourceGroup>/providers/Microsoft.Sql/servers/<serverName>/databases/<databaseName>/providers/microsoft.insights/diagnosticSettings/<settingsName>?api-version=2017-05-01-preview
+     https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/providers/microsoft.insights/diagnosticSettings/{settingsName}?api-version=2017-05-01-preview
      For more information, see [Diagnostic Settings REST
      API](https://go.microsoft.com/fwlink/?linkid=2033207)
      or [Diagnostic Settings
diff --git a/azure-mgmt-sql/azure/mgmt/sql/models/extended_server_blob_auditing_policy.py b/azure-mgmt-sql/azure/mgmt/sql/models/extended_server_blob_auditing_policy.py
index 68813994b0be..ac110357f4b8 100644
--- a/azure-mgmt-sql/azure/mgmt/sql/models/extended_server_blob_auditing_policy.py
+++ b/azure-mgmt-sql/azure/mgmt/sql/models/extended_server_blob_auditing_policy.py
@@ -93,10 +93,10 @@ class ExtendedServerBlobAuditingPolicy(ProxyResource):
      RECEIVE
      REFERENCES
      The general form for defining an action to be audited is:
-     <action> ON <object> BY <principal>
+     {action} ON {object} BY {principal}
      Note that <object> in the above format can refer to an object like a
      table, view, or stored procedure, or an entire database or schema. For the
-     latter cases, the forms DATABASE::<db_name> and SCHEMA::<schema_name> are
+     latter cases, the forms DATABASE::{db_name} and SCHEMA::{schema_name} are
      used, respectively.
      For example:
      SELECT on dbo.myTable by public
@@ -119,10 +119,10 @@ class ExtendedServerBlobAuditingPolicy(ProxyResource):
      'SQLSecurityAuditEvents' diagnostic logs category on the database should
      be also created.
      Note that for server level audit you should use the 'master' database as
-     <databaseName>.
+     {databaseName}.
      Diagnostic Settings URI format:
      PUT
-     https://management.azure.com/subscriptions/<subscriptionId>/resourceGroups/<resourceGroup>/providers/Microsoft.Sql/servers/<serverName>/databases/<databaseName>/providers/microsoft.insights/diagnosticSettings/<settingsName>?api-version=2017-05-01-preview
+     https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/providers/microsoft.insights/diagnosticSettings/{settingsName}?api-version=2017-05-01-preview
      For more information, see [Diagnostic Settings REST
      API](https://go.microsoft.com/fwlink/?linkid=2033207)
      or [Diagnostic Settings
diff --git a/azure-mgmt-sql/azure/mgmt/sql/models/extended_server_blob_auditing_policy_py3.py b/azure-mgmt-sql/azure/mgmt/sql/models/extended_server_blob_auditing_policy_py3.py
index 1f60403ce96c..89b96febe17d 100644
--- a/azure-mgmt-sql/azure/mgmt/sql/models/extended_server_blob_auditing_policy_py3.py
+++ b/azure-mgmt-sql/azure/mgmt/sql/models/extended_server_blob_auditing_policy_py3.py
@@ -93,10 +93,10 @@ class ExtendedServerBlobAuditingPolicy(ProxyResource):
      RECEIVE
      REFERENCES
      The general form for defining an action to be audited is:
-     <action> ON <object> BY <principal>
+     {action} ON {object} BY {principal}
      Note that <object> in the above format can refer to an object like a
      table, view, or stored procedure, or an entire database or schema. For the
-     latter cases, the forms DATABASE::<db_name> and SCHEMA::<schema_name> are
+     latter cases, the forms DATABASE::{db_name} and SCHEMA::{schema_name} are
      used, respectively.
      For example:
      SELECT on dbo.myTable by public
@@ -119,10 +119,10 @@ class ExtendedServerBlobAuditingPolicy(ProxyResource):
      'SQLSecurityAuditEvents' diagnostic logs category on the database should
      be also created.
      Note that for server level audit you should use the 'master' database as
-     <databaseName>.
+     {databaseName}.
      Diagnostic Settings URI format:
      PUT
-     https://management.azure.com/subscriptions/<subscriptionId>/resourceGroups/<resourceGroup>/providers/Microsoft.Sql/servers/<serverName>/databases/<databaseName>/providers/microsoft.insights/diagnosticSettings/<settingsName>?api-version=2017-05-01-preview
+     https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/providers/microsoft.insights/diagnosticSettings/{settingsName}?api-version=2017-05-01-preview
      For more information, see [Diagnostic Settings REST
      API](https://go.microsoft.com/fwlink/?linkid=2033207)
      or [Diagnostic Settings
diff --git a/azure-mgmt-sql/azure/mgmt/sql/models/server_blob_auditing_policy.py b/azure-mgmt-sql/azure/mgmt/sql/models/server_blob_auditing_policy.py
index e100e6d3b95c..9a7bc69b8c5d 100644
--- a/azure-mgmt-sql/azure/mgmt/sql/models/server_blob_auditing_policy.py
+++ b/azure-mgmt-sql/azure/mgmt/sql/models/server_blob_auditing_policy.py
@@ -90,10 +90,10 @@ class ServerBlobAuditingPolicy(ProxyResource):
      RECEIVE
      REFERENCES
      The general form for defining an action to be audited is:
-     <action> ON <object> BY <principal>
+     {action} ON {object} BY {principal}
      Note that <object> in the above format can refer to an object like a
      table, view, or stored procedure, or an entire database or schema. For the
-     latter cases, the forms DATABASE::<db_name> and SCHEMA::<schema_name> are
+     latter cases, the forms DATABASE::{db_name} and SCHEMA::{schema_name} are
      used, respectively.
      For example:
      SELECT on dbo.myTable by public
@@ -116,10 +116,10 @@ class ServerBlobAuditingPolicy(ProxyResource):
      'SQLSecurityAuditEvents' diagnostic logs category on the database should
      be also created.
      Note that for server level audit you should use the 'master' database as
-     <databaseName>.
+     {databaseName}.
      Diagnostic Settings URI format:
      PUT
-     https://management.azure.com/subscriptions/<subscriptionId>/resourceGroups/<resourceGroup>/providers/Microsoft.Sql/servers/<serverName>/databases/<databaseName>/providers/microsoft.insights/diagnosticSettings/<settingsName>?api-version=2017-05-01-preview
+     https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/providers/microsoft.insights/diagnosticSettings/{settingsName}?api-version=2017-05-01-preview
      For more information, see [Diagnostic Settings REST
      API](https://go.microsoft.com/fwlink/?linkid=2033207)
      or [Diagnostic Settings
diff --git a/azure-mgmt-sql/azure/mgmt/sql/models/server_blob_auditing_policy_py3.py b/azure-mgmt-sql/azure/mgmt/sql/models/server_blob_auditing_policy_py3.py
index 183f99e50113..120d066e6427 100644
--- a/azure-mgmt-sql/azure/mgmt/sql/models/server_blob_auditing_policy_py3.py
+++ b/azure-mgmt-sql/azure/mgmt/sql/models/server_blob_auditing_policy_py3.py
@@ -90,10 +90,10 @@ class ServerBlobAuditingPolicy(ProxyResource):
      RECEIVE
      REFERENCES
      The general form for defining an action to be audited is:
-     <action> ON <object> BY <principal>
+     {action} ON {object} BY {principal}
      Note that <object> in the above format can refer to an object like a
      table, view, or stored procedure, or an entire database or schema. For the
-     latter cases, the forms DATABASE::<db_name> and SCHEMA::<schema_name> are
+     latter cases, the forms DATABASE::{db_name} and SCHEMA::{schema_name} are
      used, respectively.
      For example:
      SELECT on dbo.myTable by public
@@ -116,10 +116,10 @@ class ServerBlobAuditingPolicy(ProxyResource):
      'SQLSecurityAuditEvents' diagnostic logs category on the database should
      be also created.
      Note that for server level audit you should use the 'master' database as
-     <databaseName>.
+     {databaseName}.
      Diagnostic Settings URI format:
      PUT
-     https://management.azure.com/subscriptions/<subscriptionId>/resourceGroups/<resourceGroup>/providers/Microsoft.Sql/servers/<serverName>/databases/<databaseName>/providers/microsoft.insights/diagnosticSettings/<settingsName>?api-version=2017-05-01-preview
+     https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/providers/microsoft.insights/diagnosticSettings/{settingsName}?api-version=2017-05-01-preview
      For more information, see [Diagnostic Settings REST
      API](https://go.microsoft.com/fwlink/?linkid=2033207)
      or [Diagnostic Settings