Update elastic-jobs-overview.md (#34541)

Author: sravanisaluru

azure-sql/database/elastic-jobs-overview.md

@@ -324,7 +324,7 @@ These are the current limitations to the elastic jobs service. We're actively wo
 | Issue | Description |
 | :--- | :--- |
 | The elastic job agent needs to be recreated and started in the new region after a failover/move to a new Azure region. | The elastic jobs service stores all its job agent and job metadata in the jobs database. Any failover or move of Azure resources to a new Azure region will also move the jobs database, job agent, and job metadata to the new Azure region. However, the elastic job agent is a compute only resource and needs to be explicitly re-created and started in the new region before jobs will start executing again in the new region. Once started, the elastic job agent will resume executing jobs in the new region as per the previously defined job schedule.|
-| Excessive Audit logs from jobs database | The elastic job agent operates by constantly polling the job database to check for the arrival of new jobs and other CRUD operations. If auditing is enabled on the server that houses a jobs database, a large number of audit logs can be generated by the jobs database. This can be mitigated by filtering out these audit logs using the `Set-AzSqlServerAudit` command with a predicate expression.<br /><br />For example:<br />`Set-AzSqlServerAudit -ResourceGroupName "ResourceGroup01" -ServerName "Server01" -BlobStorageTargetState Enabled -StorageAccountResourceId "/subscriptions/7fe3301d-31d3-4668-af5e-211a890ba6e3/resourceGroups/resourcegroup01/providers/Microsoft.Storage/storageAccounts/mystorage" -PredicateExpression "database_principal_name <> '##MS_JobAccount##'"`<br />This command will only filter out job agent to jobs database audit logs, not job agent to any target databases audit logs. |
+| Excessive Audit logs from jobs database | The elastic job agent operates by constantly polling the job database to check for the arrival of new jobs and other CRUD operations. If auditing is enabled on the server that houses a jobs database, a large number of audit logs can be generated by the jobs database. This can be mitigated by filtering out these audit logs using the `Set-AzSqlServerAudit` command with a predicate expression.<br /><br />For example:<br />`Set-AzSqlServerAudit -ResourceGroupName "ResourceGroup01" -ServerName "Server01" -BlobStorageTargetState Enabled -StorageAccountResourceId "/subscriptions/7fe3301d-31d3-4668-af5e-211a890ba6e3/resourceGroups/resourcegroup01/providers/Microsoft.Storage/storageAccounts/mystorage" -PredicateExpression "application_name <> 'Microsoft Azure SQL Database elastic jobs'"`<br />This command will only filter out job agent to jobs database audit logs, not job agent to any target databases audit logs. |
 | Use of a Hyperscale database as *job database* | Using a Hyperscale database as a *job database* isn't supported. However, elastic jobs can target Hyperscale databases in the same way as any other database in Azure SQL Database. |
 | Serverless databases and auto-pausing with elastic jobs. | Auto-pause enabled serverless database isn't supported as a *job database*. Serverless databases targeted by elastic jobs do support auto-pausing, and will be resumed by job connections. |
 | Export a *Job Database* to a BACPAC file | Export of a *Job Database* to a BACPAC file is not supported. If the SQL Server containing a *Job Database* needs to be exported, *Job Database* should be dropped first before exporting the server. |