|
| 1 | +--- |
| 2 | +title: Sovereign cloud feature variations |
| 3 | +description: List of feature variations and usage limitations for Advisor in sovereign clouds. |
| 4 | +ms.topic: article |
| 5 | +ms.date: 09/19/2022 |
| 6 | +--- |
| 7 | + |
| 8 | +# Azure Advisor in sovereign clouds |
| 9 | + |
| 10 | +Azure sovereign clouds enable you to build and digitally transform workloads in the cloud while meeting your security, compliance, and policy requirements. |
| 11 | + |
| 12 | +## Azure Government (United States) |
| 13 | + |
| 14 | +The following Azure Advisor recommendation **features aren't currently available** in Azure Government: |
| 15 | + |
| 16 | +### Cost |
| 17 | + |
| 18 | +- (Preview) Consider App Service stamp fee reserved capacity to save over your on-demand costs. |
| 19 | +- (Preview) Consider Azure Data Explorer reserved capacity to save over your pay-as-you-go costs. |
| 20 | +- (Preview) Consider Azure Synapse Analytics (formerly SQL DW) reserved capacity to save over your pay-as-you-go costs. |
| 21 | +- (Preview) Consider Blob storage reserved capacity to save on Blob v2 and Data Lake Storage Gen2 costs. |
| 22 | +- (Preview) Consider Blob storage reserved instance to save on Blob v2 and Data Lake Storage Gen2 costs. |
| 23 | +- (Preview) Consider Cache for Redis reserved capacity to save over your pay-as-you-go costs. |
| 24 | +- (Preview) Consider Cosmos DB reserved capacity to save over your pay-as-you-go costs. |
| 25 | +- (Preview) Consider Database for MariaDB reserved capacity to save over your pay-as-you-go costs. |
| 26 | +- (Preview) Consider Database for MySQL reserved capacity to save over your pay-as-you-go costs. |
| 27 | +- (Preview) Consider Database for PostgreSQL reserved capacity to save over your pay-as-you-go costs. |
| 28 | +- (Preview) Consider SQL DB reserved capacity to save over your pay-as-you-go costs. |
| 29 | +- (Preview) Consider SQL PaaS DB reserved capacity to save over your pay-as-you-go costs. |
| 30 | +- Consider App Service stamp fee reserved instance to save over your on-demand costs. |
| 31 | +- Consider Azure Synapse Analytics (formerly SQL DW) reserved instance to save over your pay-as-you-go costs. |
| 32 | +- Consider Cache for Redis reserved instance to save over your pay-as-you-go costs. |
| 33 | +- Consider Cosmos DB reserved instance to save over your pay-as-you-go costs. |
| 34 | +- Consider Database for MariaDB reserved instance to save over your pay-as-you-go costs. |
| 35 | +- Consider Database for MySQL reserved instance to save over your pay-as-you-go costs. |
| 36 | +- Consider Database for PostgreSQL reserved instance to save over your pay-as-you-go costs. |
| 37 | +- Consider SQL PaaS DB reserved instance to save over your pay-as-you-go costs. |
| 38 | + |
| 39 | +## Operational |
| 40 | + |
| 41 | +- Add Azure Monitor to your virtual machine (VM) labeled as production. |
| 42 | +- Delete and recreate your pool using a VM size that will soon be retired. |
| 43 | +- Enable Traffic Analytics to view insights into traffic patterns across Azure resources. |
| 44 | +- Enforce 'Add or replace a tag on resources' using Azure Policy. |
| 45 | +- Enforce 'Allowed locations' using Azure Policy. |
| 46 | +- Enforce 'Allowed virtual machine SKUs' using Azure Policy. |
| 47 | +- Enforce 'Audit VMs that don't use managed disks' using Azure Policy. |
| 48 | +- Enforce 'Inherit a tag from the resource group' using Azure Policy. |
| 49 | +- Update Azure Spring Cloud API Version. |
| 50 | +- Update your outdated Azure Spring Cloud SDK to the latest version. |
| 51 | +- Upgrade to the latest version of the Immersive Reader SDK. |
| 52 | + |
| 53 | +### Performance |
| 54 | + |
| 55 | +- Accelerated Networking may require stopping and starting the VM. |
| 56 | +- Arista Networks vEOS Router may experience high CPU utilization, reduced throughput and high latency. |
| 57 | +- Barracuda Networks NextGen Firewall may experience high CPU utilization, reduced throughput and high latency. |
| 58 | +- Cisco Cloud Services Router 1000V may experience high CPU utilization, reduced throughput and high latency. |
| 59 | +- Consider increasing the size of your NVA to address persistent high CPU. |
| 60 | +- Distribute data in server group to distribute workload among nodes. |
| 61 | +- More than 75% of your queries are full scan queries. |
| 62 | +- NetApp Cloud Volumes ONTAP may experience high CPU utilization, reduced throughput and high latency. |
| 63 | +- Palo Alto Networks VM-Series Firewall may experience high CPU utilization, reduced throughput and high latency. |
| 64 | +- Reads happen on most recent data. |
| 65 | +- Rebalance data in Hyperscale (Citus) server group to distribute workload among worker nodes more evenly. |
| 66 | +- Update Attestation API Version. |
| 67 | +- Update Key Vault SDK Version. |
| 68 | +- Update to the latest version of your Arista VEOS product for Accelerated Networking support. |
| 69 | +- Update to the latest version of your Barracuda NG Firewall product for Accelerated Networking support. |
| 70 | +- Update to the latest version of your Check Point product for Accelerated Networking support. |
| 71 | +- Update to the latest version of your Cisco Cloud Services Router 1000V product for Accelerated Networking support. |
| 72 | +- Update to the latest version of your F5 BigIp product for Accelerated Networking support. |
| 73 | +- Update to the latest version of your NetApp product for Accelerated Networking support. |
| 74 | +- Update to the latest version of your Palo Alto Firewall product for Accelerated Networking support. |
| 75 | +- Upgrade your ExpressRoute circuit bandwidth to accommodate your bandwidth needs. |
| 76 | +- Use SSD Disks for your production workloads. |
| 77 | +- vSAN capacity utilization has crossed critical threshold. |
| 78 | + |
| 79 | +### Reliability |
| 80 | + |
| 81 | +- Avoid hostname override to ensure site integrity. |
| 82 | +- Check Point Virtual Machine may lose Network Connectivity. |
| 83 | +- Drop and recreate your HDInsight clusters to apply critical updates. |
| 84 | +- Upgrade device client SDK to a supported version for IotHub. |
| 85 | +- Upgrade to the latest version of the Azure Connected Machine agent. |
| 86 | + |
| 87 | +## Right size calculations |
| 88 | + |
| 89 | +The calculation for recommending that you should right-size or shut down underutilized virtual machines in Azure Government is as follows: |
| 90 | + |
| 91 | +- Advisor monitors your virtual machine usage for seven days and identifies low-utilization virtual machines. |
| 92 | +- Virtual machines are considered low utilization if their CPU utilization is 5% or less and their network utilization is less than 2%, or if the current workload can be accommodated by a smaller virtual machine size. |
| 93 | + |
| 94 | +If you want to be more aggressive at identifying underutilized virtual machines, you can adjust the CPU utilization rule on a per subscription basis. |
| 95 | + |
| 96 | +## Next steps |
| 97 | + |
| 98 | +For more information about Advisor recommendations, see: |
| 99 | + |
| 100 | +- [Introduction to Azure Advisor](./advisor-overview.md) |
| 101 | +- [Reliability recommendations](./advisor-high-availability-recommendations.md) |
| 102 | +- [Performance recommendations](./advisor-reference-performance-recommendations.md) |
| 103 | +- [Cost recommendations](./advisor-reference-cost-recommendations.md) |
| 104 | +- [Operational excellence recommendations](./advisor-reference-operational-excellence-recommendations.md) |
0 commit comments