Merge branch 'main' into copilot/fix-85f15788-a0b8-4e52-bc90-ebff04f64f28

Author: tksh164

azure-resources/Network/privateDnsZones/recommendations.yaml

@@ -32,23 +32,6 @@
     - name: Azure Monitor Baseline Alerts - privateDnsZones
       url: "https://azure.github.io/azure-monitor-baseline-alerts/services/Network/privateDnsZones/"
 
-- description: Use regional Private DNS Zones when there is a low recovery time objective (RTO) requirement
-  aprlGuid: 1e02335c-1f90-fd4e-a5a5-d359c7b22d70
-  recommendationTypeId: null
-  recommendationControl: DisasterRecovery
-  recommendationImpact: Medium
-  recommendationResourceType: Microsoft.Network/privateDnsZones
-  recommendationMetadataState: Active
-  longDescription: |
-    For business continuity scenarios with a low recovery time objective (RTO), ensure that distinct regional production and disaster recovery (DR) Private DNS Zones are configured and have identical workload and resource DNS entries. This keeps DNS resolution consistent across both zones.
-  potentialBenefits: Ensures seamless failover for DNS during a regional outage
-  pgVerified: true
-  automationAvailable: false
-  tags: []
-  learnMoreLink:
-    - name: Private Link and DNS integration at scale
-      url: "https://learn.microsoft.com/azure/cloud-adoption-framework/ready/azure-best-practices/private-link-and-dns-integration-at-scale"
-
 - description: Ensure Time-To-Live (TTL) is set appropriately to ensure RTOs can be met
   aprlGuid: 3538aa48-c40b-455b-a93b-269fe6e65be2
   recommendationTypeId: null

azure-resources/Oracledatabase/_index.md

@@ -0,0 +1,5 @@
+---
+title: "Oracledatabase"
+geekdocCollapseSection: true
+geekdocHidden: false
+---

azure-resources/Oracledatabase/cloudexadatainfrastructures/_index.md

@@ -0,0 +1,7 @@
+---
+title: "Cloudexadatainfrastructures"
+geekdocCollapseSection: true
+geekdocHidden: false
+---
+
+{{< azure-resources-recommendationlist name="azure-resources-recommendationlist" >}}

…1e02335c-1f90-fd4e-a5a5-d359c7b22d70.kql …c99d730b-8754-447f-bd5d-3e8850a12235.kqlazure-resources/Network/privateDnsZones/kql/1e02335c-1f90-fd4e-a5a5-d359c7b22d70.kql renamed to azure-resources/Oracledatabase/cloudexadatainfrastructures/kql/c99d730b-8754-447f-bd5d-3e8850a12235.kql azure-resources/Network/privateDnsZones/kql/1e02335c-1f90-fd4e-a5a5-d359c7b22d70.kql renamed to azure-resources/Oracledatabase/cloudexadatainfrastructures/kql/c99d730b-8754-447f-bd5d-3e8850a12235.kql

@@ -1,2 +1 @@
 // under-development
-

azure-resources/Oracledatabase/cloudexadatainfrastructures/recommendations.yaml

@@ -0,0 +1,17 @@
+- description: Ensure ODAA infrastructure is in Available state under normal operations
+  aprlGuid: c99d730b-8754-447f-bd5d-3e8850a12235
+  recommendationTypeId: null
+  recommendationControl: OtherBestPractices
+  recommendationImpact: High
+  recommendationResourceType: Oracle.Database/cloudExadataInfrastructures
+  recommendationMetadataState: Active
+  longDescription: |
+    ODAA Exadata infrastructures can be in a number of states during its lifecycle (Available, Failed, Maintenance In Progress, Provisioning, Terminated, Terminating and Updating).
+    Ensure that the infrastructure is in Available state under normal operations.
+  potentialBenefits: Ensure service is available
+  pgVerified: false
+  automationAvailable: false
+  tags: []
+  learnMoreLink:
+    - name: Cloud Exadata infrastructure lifecycle
+      url: "https://learn.microsoft.com/rest/api/oracle/cloud-exadata-infrastructures/get?view=rest-oracle-2023-09-01&tabs=HTTP#cloudexadatainfrastructurelifecyclestate"

azure-resources/Oracledatabase/cloudexadatavmclusters/_index.md

@@ -0,0 +1,7 @@
+---
+title: "Cloudvmclusters"
+geekdocCollapseSection: true
+geekdocHidden: false
+---
+
+{{< azure-resources-recommendationlist name="azure-resources-recommendationlist" >}}

azure-resources/Oracledatabase/cloudexadatavmclusters/kql/4b33324a-70cd-4bac-bdae-da4c382c436b.kql

@@ -0,0 +1 @@
+// under-development

azure-resources/Oracledatabase/cloudexadatavmclusters/recommendations.yaml

@@ -0,0 +1,17 @@
+- description: Ensure ODAA clusters are in Available state under normal operations
+  aprlGuid: 4b33324a-70cd-4bac-bdae-da4c382c436b
+  recommendationTypeId: null
+  recommendationControl: OtherBestPractices
+  recommendationImpact: High
+  recommendationResourceType: Oracle.Database/cloudVmClusters
+  recommendationMetadataState: Active
+  longDescription: |
+    ODAA Vm Clusters can be in a number of states during their lifecycle (Available, Failed, Maintenance In Progress, Provisioning, Terminated, Terminating and Updating).
+    Ensure that the ODAA clusters are in Available state under normal operations.
+  potentialBenefits: Ensure service is available
+  pgVerified: false
+  automationAvailable: false
+  tags: []
+  learnMoreLink:
+    - name: Cloud VM Cluster lifecycle
+      url: "https://learn.microsoft.com/rest/api/oracle/cloud-vm-clusters/get?view=rest-oracle-2023-09-01&tabs=HTTP#cloudvmclusterlifecyclestate"

azure-resources/Sql/servers/recommendations.yaml

@@ -72,7 +72,7 @@
   recommendationControl: MonitoringAndAlerting
   recommendationImpact: High
   recommendationResourceType: Microsoft.Sql/servers/databases
-  recommendationMetadataState: Active
+  recommendationMetadataState: Disabled
   longDescription: |
     Monitoring and alerting are an important part of database operations. When working with Azure SQL Database, make use of Azure Monitor and SQL Insights to ensure that you capture relevant database metrics.
   potentialBenefits: Quick incident detection and response

azure-specialized-workloads/oracle/recommendations.yaml

@@ -11,7 +11,7 @@
     Use SYNC for zero data loss or ASYNC when performance is constrained.
   potentialBenefits: Ensure business continuity in case of zonal failure.
   pgVerified: false
-  automationAvailable: no
+  automationAvailable: false
   tags: [ORACLE]
   learnMoreLink:
     - name: Business continuity and disaster recovery considerations for Oracle Database@Azure
@@ -28,7 +28,7 @@
     Gold-level reference architecture with Oracle Database@Azure is recommended, meaning that database changes will be replicated via Data Guard (ASYNC replication) to a secondary Oracle Database@Azure instance in a different region.
   potentialBenefits: The cloud MAA architecture achieves data protection and DR.
   pgVerified: false
-  automationAvailable: no
+  automationAvailable: false
   tags: [ORACLE]
   learnMoreLink:
     - name: Business continuity and disaster recovery considerations for Oracle Database@Azure
@@ -46,7 +46,7 @@
     ARS provides automated, policy-based backups with continuous validation.
   potentialBenefits: Provide workload data protection.
   pgVerified: false
-  automationAvailable: no
+  automationAvailable: false
   tags: [ORACLE]
   learnMoreLink:
     - name: Business continuity and disaster recovery considerations for Oracle Database@Azure
@@ -65,7 +65,7 @@
     If needed, scale OCPUs on the VM cluster, if Exa infrastructure capacity allows.
   potentialBenefits: Meet workload scalability requirements.
   pgVerified: false
-  automationAvailable: no
+  automationAvailable: false
   tags: [ORACLE]
   learnMoreLink:
     - name: Learn about Manage and monitor Oracle Database@Azure
@@ -83,7 +83,7 @@
     Primary, standby, client, and backup subnets should have non-overlapping CIDR ranges for reliable connectivity.
   potentialBenefits: Avoid conflicts in IP addressing.
   pgVerified: false
-  automationAvailable: no
+  automationAvailable: false
   tags: [ORACLE]
   learnMoreLink:
     - name: Capacity planning for Oracle Database@Azure
@@ -100,7 +100,7 @@
     Deploy Data Guard observer nodes in different AZs and make sure that an observer node will remain available if anything happens to the Production deployment.
   potentialBenefits: Data Guard observer automates database failover.
   pgVerified: false
-  automationAvailable: no
+  automationAvailable: false
   tags: [ORACLE]
   learnMoreLink:
     - name: Business continuity and disaster recovery considerations for Oracle Database@Azure
@@ -117,7 +117,7 @@
     Provide redundancy for VMs used as OKV, note that this is only relevant if customer is using own keys and only if OCI vault is not used. A minimum 4-node OKV cluster deployment is recommended across two AZs or regions, aligned with the BCDR architecture.
   potentialBenefits: Protect access to keys in case of VM or AZ/region failure.
   pgVerified: false
-  automationAvailable: no
+  automationAvailable: false
   tags: [ORACLE]
   learnMoreLink:
     - name: Security guidelines for Oracle Database@Azure
@@ -135,7 +135,7 @@
     Automatic infrastructure maintenance occurs quarterly, with Oracle notifying you of the date and time weeks in advance. You can modify the scheduled date and time before maintenance starts.
   potentialBenefits: Keep Oracle workloads up-to-date.
   pgVerified: false
-  automationAvailable: no
+  automationAvailable: false
   tags: [ORACLE]
   learnMoreLink:
     - name: Configure Oracle-Managed Infrastructure Maintenance