Merge pull request #263012 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: rmca14

articles/app-service/scripts/cli-continuous-deployment-vsts.md

@@ -36,7 +36,7 @@ Create the following variables containing your Azure DevOps information.
 
 ```azurecli
 gitrepo=<Replace with your Azure DevOps Services (formerly Visual Studio Team Services, or VSTS) repo URL>
-token=<Replace with a Azure DevOps Services (formerly Visual Studio Team Services, or VSTS) personal access token>
+token=<Replace with an Azure DevOps Services (formerly Visual Studio Team Services, or VSTS) personal access token>
 ```
 
 Configure continuous deployment from Azure DevOps Services (formerly Visual Studio Team Services, or VSTS). The `--git-token` parameter is required only once per Azure account (Azure remembers token).

articles/azure-resource-manager/bicep/bicep-config.md

@@ -8,9 +8,9 @@ ms.date: 09/27/2023
 
 # Configure your Bicep environment
 
-Bicep supports a configuration file named `bicepconfig.json`. Within this file, you can add values that customize your Bicep development experience. If you don't add this file, Bicep uses default values.
+Bicep supports an optional configuration file named `bicepconfig.json`. Within this file, you can add values that customize your Bicep development experience.
 
-To customize values, create this file in the directory where you store Bicep files. You can add `bicepconfig.json` files in multiple directories. The configuration file closest to the Bicep file in the directory hierarchy is used.
+To customize configuration, create this file in the same directory, or a parent directory of your Bicep files. If multiple parent directories contain `bicepconfig.json` files, Bicep uses configuration from the nearest one. If a configuration file is not found, Bicep uses default values.
 
 To configure Bicep extension settings, see [VS Code and Bicep extension](./install.md#visual-studio-code-and-bicep-extension).
 
@@ -36,30 +36,20 @@ The [Bicep linter](linter.md) checks Bicep files for syntax errors and best prac
 
 ## Enable experimental features
 
-You can enable preview features by adding:
+You can enable experimental features by adding the following section to your `bicepconfig.json` file.
+
+Here is an example of enabling features 'compileTimeImports' and 'userDefinedFunctions`. 
 
 ```json
 {
   "experimentalFeaturesEnabled": {
-    "userDefinedTypes": true,
-    "extensibility": true
+    "compileTimeImports": true,
+    "userDefinedFunctions": true
   }
 }
 ```
 
-> [!WARNING]
-> To utilize the experimental features, it's necessary to have the latest version of [Azure CLI](./install.md#azure-cli).
-
-The preceding sample enables 'userDefineTypes' and 'extensibility`. The available experimental features include:
-
-- **assertions**: Should be enabled in tandem with `testFramework` experimental feature flag for expected functionality. Allows you to author boolean assertions using the `assert` keyword comparing the actual value of a parameter, variable, or resource name to an expected value. Assert statements can only be written directly within the Bicep file whose resources they reference. For more information, see [Bicep Experimental Test Framework](https://github.com/Azure/bicep/issues/11967).
-- **compileTimeImports**: Allows you to use symbols defined in another Bicep file. See [Import types, variables and functions](./bicep-import.md#import-types-variables-and-functions-preview).
-- **extensibility**: Allows Bicep to use a provider model to deploy non-ARM resources. Currently, we only support a Kubernetes provider. See [Bicep extensibility Kubernetes provider](./bicep-extensibility-kubernetes-provider.md).
-- **sourceMapping**: Enables basic source mapping to map an error location returned in the ARM template layer back to the relevant location in the Bicep file.
-- **resourceTypedParamsAndOutputs**: Enables the type for a parameter or output to be of type resource to make it easier to pass resource references between modules. This feature is only partially implemented. See [Simplifying resource referencing](https://github.com/azure/bicep/issues/2245).
-- **symbolicNameCodegen**: Allows the ARM template layer to use a new schema to represent resources as an object dictionary rather than an array of objects. This feature improves the semantic equivalent of the Bicep and ARM templates, resulting in more reliable code generation. Enabling this feature has no effect on the Bicep layer's functionality.
-- **testFramework**: Should be enabled in tandem with `assertions` experimental feature flag for expected functionality. Allows you to author client-side, offline unit-test test blocks that reference Bicep files and mock deployment parameters in a separate `test.bicep` file using the new `test` keyword. Test blocks can be run with the command *bicep test <filepath_to_file_with_test_blocks>* which runs all `assert` statements in the Bicep files referenced by the test blocks. For more information, see [Bicep Experimental Test Framework](https://github.com/Azure/bicep/issues/11967).
-- **userDefinedFunctions**: Allows you to define your own custom functions. See [User-defined functions in Bicep](./user-defined-functions.md).
+For information on the current set of experimental features, see [Experimental Features](https://aka.ms/bicep/experimental-features).
 
 ## Next steps
 

articles/azure-resource-manager/bicep/user-defined-data-types.md

@@ -146,7 +146,7 @@ The valid type expressions include:
     type mixedTypeArray = ('fizz' | 42 | {an: 'object'} | null)[]
     ```
 
-In addition to be used in the `type` statement, type expressions can also be used in these places for creating user-defined date types:
+In addition to be used in the `type` statement, type expressions can also be used in these places for creating user-defined data types:
 
 - As the type clause of a `param` statement. For example:
 

articles/hdinsight/hdinsight-custom-ambari-db.md

@@ -32,7 +32,17 @@ The custom Ambari DB has the following other requirements:
 - The name of the database cannot contain hyphens or spaces
 - You must have an existing Azure SQL DB server and database.
 - The database that you provide for Ambari setup must be empty. There should be no tables in the default dbo schema.
-- The user used to connect to the database should have SELECT, CREATE TABLE, and INSERT permissions on the database.
+- The user used to connect to the database should have **SELECT, CREATE TABLE, INSERT, UPDATE, DELETE, ALTER ON SCHEMA and REFERENCES ON SCHEMA** permissions on the database.
+```sql
+GRANT CREATE TABLE TO newuser;
+GRANT INSERT TO newuser;
+GRANT SELECT TO newuser;
+GRANT UPDATE TO newuser;
+GRANT DELETE TO newuser;
+GRANT ALTER ON SCHEMA::dbo TO newuser;
+GRANT REFERENCES ON SCHEMA::dbo TO newuser;
+```
+
 - Turn on the option to [Allow access to Azure services](/azure/azure-sql/database/vnet-service-endpoint-rule-overview#azure-portal-steps) on the server where you host Ambari.
 - Management IP addresses from HDInsight service need to be allowed in the firewall rule. See [HDInsight management IP addresses](hdinsight-management-ip-addresses.md) for a list of the IP addresses that must be added to the server-level firewall rule.
 

articles/search/search-indexer-overview.md

@@ -19,7 +19,7 @@ An *indexer* in Azure AI Search is a crawler that extracts textual data from clo
 
 Indexers also drive [skillset execution and AI enrichment](cognitive-search-concept-intro.md), where you can configure skills to integrate extra processing of content en route to an index. A few examples are OCR over image files, text split skill for data chunking, text translation for multiple languages.
 
-Indexers target[supported data sources](#supported-data-sources). An indexer configuration specifies a data source (origin) and a search index (destination). Several sources, such as Azure Blob Storage, have more configuration properties specific to that content type.
+Indexers target [supported data sources](#supported-data-sources). An indexer configuration specifies a data source (origin) and a search index (destination). Several sources, such as Azure Blob Storage, have more configuration properties specific to that content type.
 
 You can run indexers on demand or on a recurring data refresh schedule that runs as often as every five minutes. More frequent updates require a ['push model'](search-what-is-data-import.md) that simultaneously updates data in both Azure AI Search and your external data source.
 

articles/sentinel/create-codeless-connector-legacy.md

@@ -622,7 +622,7 @@ Use one of the following methods:
 
 - **Azure portal**: In your Microsoft Sentinel data connector page, select **Disconnect**.
 
-- **API**: Use the [DISCONNECT](/rest/api/securityinsights/preview/data-connectors/disconnect) API to send a PUT call with an empty body to the following URL:
+- **API**: Use the *DISCONNECT* API to send a PUT call with an empty body to the following URL:
 
     ```http
     https://management.azure.com /subscriptions/{{SUB}}/resourceGroups/{{RG}}/providers/Microsoft.OperationalInsights/workspaces/{{WS-NAME}}/providers/Microsoft.SecurityInsights/dataConnectors/{{Connector_Id}}/disconnect?api-version=2021-03-01-preview

articles/sentinel/workspace-manager.md

@@ -124,7 +124,7 @@ Common reasons for failure include:
 ### API references
 - [Workspace Manager Assignment Jobs](/rest/api/securityinsights/preview/workspace-manager-assignment-jobs)
 - [Workspace Manager Assignments](/rest/api/securityinsights/preview/workspace-manager-assignments)
-- [Workspace Manager Configurations](/rest/api/securityinsights/preview/workspace-manager-configurations)
+- *Workspace Manager Configurations*
 - [Workspace Manager Groups](/rest/api/securityinsights/preview/workspace-manager-groups)
 - [Workspace Manager Members](/rest/api/securityinsights/preview/workspace-manager-members)
 

articles/spring-apps/basic-standard/breadcrumb/toc.yml

@@ -5,8 +5,4 @@ items:
   items:
   - name: Azure Spring Apps
     tocHref: /azure/spring-apps
-    topicHref: /azure/spring-apps/index
-    items:
-    - name: Basic/Standard plan
-      tocHref: /
-      topicHref: /azure/spring-apps/basic-standard/index
+    topicHref: /azure/spring-apps/index 

articles/spring-apps/consumption-dedicated/breadcrumb/toc.yml

@@ -5,8 +5,4 @@ items:
   items:
   - name: Azure Spring Apps
     tocHref: /azure/spring-apps
-    topicHref: /azure/spring-apps/index
-    items:
-    - name: Standard consumption and dedicated plan
-      tocHref: /
-      topicHref: /azure/spring-apps/consumption-dedicated/index
+    topicHref: /azure/spring-apps/index 

articles/spring-apps/enterprise/breadcrumb/toc.yml

@@ -5,8 +5,4 @@ items:
   items:
   - name: Azure Spring Apps
     tocHref: /azure/spring-apps
-    topicHref: /azure/spring-apps/index
-    items:
-    - name: Enterprise plan
-      tocHref: /
-      topicHref: /azure/spring-apps/enterprise/index
+    topicHref: /azure/spring-apps/index