Merge pull request #299325 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: v-alje

articles/azure-functions/functions-deploy-container-apps.md

@@ -84,7 +84,7 @@ Use these commands to create your required Azure resources:
     principalId=$(az identity create --name <USER_IDENTITY_NAME> --resource-group AzureFunctionsContainers-rg --location eastus --query principalId -o tsv) 
     acrId=$(az acr show --name <REGISTRY_NAME> --query id --output tsv)
     az role assignment create --assignee-object-id $principalId --assignee-principal-type ServicePrincipal --role acrpull --scope $acrId
-    storageId=$(az storage account show --resource-group AzureFunctionsContainers-rg --name glengatestaca2 --query 'id' -o tsv)
+    storageId=$(az storage account show --resource-group AzureFunctionsContainers-rg --name <STORAGE_NAME> --query 'id' -o tsv)
     az role assignment create --assignee-object-id $principalId --assignee-principal-type ServicePrincipal --role "Storage Blob Data Owner" --scope $storageId
     ```
 

articles/azure-functions/functions-monitoring.md

@@ -88,7 +88,7 @@ In [C#](functions-dotnet-class-library.md#log-custom-telemetry-in-c-functions),
 
 ### Dependencies
 
-Starting with version 2.x of Functions, Application Insights automatically collects data on dependencies for bindings that use certain client SDKs. Application Insights distributed tracing and dependency tracking aren't currently supported for C# apps running in an [isolated worker process](dotnet-isolated-process-guide.md). Application Insights collects data on the following dependencies:
+Starting with version 2.x of Functions, Application Insights automatically collects data on dependencies for bindings that use certain client SDKs. Application Insights collects data on the following dependencies:
 
 + Azure Cosmos DB 
 + Azure Event Hubs

articles/azure-functions/opentelemetry-howto.md

@@ -42,15 +42,6 @@ To enable OpenTelemetry output from the Functions host, update the [host.json fi
 ```json
 {
     "version": "2.0",
-    "logging": {
-        "applicationInsights": {
-            "samplingSettings": {
-                "isEnabled": true,
-                "excludedTypes": "Request"
-            },
-            "enableLiveMetricsFilters": true
-        }
-    },
     "telemetryMode": "openTelemetry"
 }
 ```

articles/sap/center-sap-solutions/monitor-portal.md

@@ -254,7 +254,19 @@ If an error appears on a successfully registered or deployed Virtual Instance fo
 3. Navigate to the VIS resource and go to the Managed Resource Group from the Essentials section on Overview. Check if a Storage Account exists in this resource group. If it exists, then check if your virtual network allows connectivity from the SAP central services VM to this storage account. Enable connectivity if needed. If the storage account doesn't exist, then you will have to delete the VIS resource and register the system again.
 4. Check if the SAP central services VM system assigned managed identity has the ‘Storage Blob Data Owner’ access on the managed resource group of the VIS. If not, provide the necessary access. If the system assigned managed identity doesn't exist, then you will have to delete the VIS and re-register the system.
 5. Ensure sapstartsrv process for the SAP instance and SAP Hostctrl is running on the Central Services VM.
-6. If everything mentioned above is in place, then log a support ticket. 
+6. If everything mentioned above is in place, then log a support ticket.
+
+### Error - Database status showed **unavailable** on the Azure portal. 
+**Possible causes:** 
+The database list has not been passed on to the HnS script args. This results in the database status to be shown as unavailable.  
+
+This can happen in 2 scenarios: 
+- SID of Database and HANA instance is not same. This would lead to db details not being discovered in the Discovery Workflow. 
+- You have multi-db cluster which will also result in this error.
+
+**Solution:**
+
+- Ensure HANA instance and its database mapped to same SID
 
 ## Next steps
 

articles/virtual-network/ip-services/private-ip-addresses.md

@@ -34,7 +34,7 @@ Private IPs allow communication to these resources without the use of a public I
 
 Azure assigns private IP addresses to resources from the address range of the virtual network subnet where the resource is.
 
-Azure reserves the first four addresses in each subnet address range. The addresses can't be assigned to resources. For example, if the subnet's address range is 10.0.0.0/16, addresses 10.0.0.0-10.0.0.3 and 10.0.255.255 are unavailable. IP addresses within the subnet's address range can only be assigned to one resource at a time. 
+Azure reserves five IP addresses in every subnet, which cannot be assigned to resources. These include the first four addresses and the last address in the subnet range. For example, in the 10.0.0.0/16 subnet, the reserved addresses are 10.0.0.0-10.0.0.3 and 10.0.255.255. All other IP addresses in the range can only be assigned to one resource at a time.
 
 There are two methods in which a private IP address is given: