Merge pull request #239327 from MicrosoftDocs/repo_sync_working_branch

Resolve syncing conflicts from repo_sync_working_branch to main

Author: huypub

articles/advisor/advisor-cost-recommendations.md

@@ -82,6 +82,10 @@ In some cases recommendations can't be adopted or might not be applicable, such
 
 In such cases, simply use the Dismiss/Postpone options associated with the recommendation. 
 
+### Limitations
+- The savings associated with the recommendations are based on retail rates and don't take into account any temporary or long-term discounts that might apply to your account. As a result, the listed savings might be higher than actually possible.  
+- The recommendations don't take into account the presence of Reserved Instances (RI) / Savings plan purchases. As a result, the listed savings might be higher than actually possible. In some cases, for example in the case of cross-series recommendations, depending on the types of SKUs that reserved instances have been purchased for, the costs might increase when the optimization recommendations are followed. We caution you to consider your RI/Savings plan purchases when you act on the right-size recommendations. 
+
 We're constantly working on improving these recommendations. Feel free to share feedback on [Advisor Forum](https://aka.ms/advisorfeedback).
 
 ## Next steps

articles/aks/monitor-apiserver.md

@@ -22,7 +22,7 @@ Kubernetes audit logging isn't enabled by default on an AKS cluster on account o
 * **Destination details:** Select the checkbox for **Log Analytics**.
 
 > [!NOTE]
-> There could be substantial cost involved once kube-audit logs are enabled. Consider disabling kube-audit logging when not required.
+> There could be substantial cost involved once kube-audit logs are enabled. Consider disabling kube-audit logging when not required. An alternative approach to significantly reduce the number of logs and help reduce cost is by enabling collection from kube-audit-admin, which excludes the get and list audit events.
 > For strategies to reduce your Azure Monitor costs, see [Cost optimization and Azure Monitor][cost-optimization-azure-monitor].
 
 After a few moments, the new setting appears in your list of settings for this resource. Logs are streamed to the specified destinations as new event data is generated. It might take up to 15 minutes between when an event is emitted and when it appears in a [Log Analytics workspace][log-analytics-workspace-overview].
@@ -63,4 +63,4 @@ For more information about AKS metrics, logs, and other important values, see [M
 [cost-optimization-azure-monitor]: ../azure-monitor/best-practices-cost.md
 [azure-diagnostics-table]: /azure/azure-monitor/reference/tables/azurediagnostics
 [container-insights-overview]: ..//azure-monitor/containers/container-insights-overview.md
-[monitoring-aks-data-reference]: monitor-aks-reference.md
+[monitoring-aks-data-reference]: monitor-aks-reference.md

articles/app-service/routine-maintenance.md

@@ -54,7 +54,7 @@ Azure App Service represents a fleet of scale units, which provide hosting of we
 
 ### Are business hours reflected?
 
-Maintenance operations are optimized to run outside standard business hours (9-5pm) as statistically that is a better timing for any interruptions and restarts of workloads as there is a less stress on the system (in customer applications and transitively also on the platform itself).
+Maintenance operations are optimized to start outside standard business hours (9-5pm) as statistically that is a better timing for any interruptions and restarts of workloads as there is a less stress on the system (in customer applications and transitively also on the platform itself). For App Service Plan and App Service Environment v2, maintenance can continue into business hours during longer maintenance events. 
 
 ### What are my options to control routine maintenance?