cost-estimation-azure.pdf

Azure Cost Estimation

March 2, 2021 Version 3

Introduction

The objective of this document is to provide Mission System Owners with a basic understanding of how to leverage the Azure cost calculator to accurately project cloud hosting costs. Topics that will be covered include:

• How to access the Azure cost calculator tool, and what are some basic usage ‘best practices’ for estimating costs in Cloud One

• Baseline costs: Managed services that are required for all Cloud One hosted systems

• Mission System resource cost estimation

• Predicting and optimizing annual operational cost

• Other resources & relevant information (Intelink invoicing)

Azure Cost Calculator:

The Basics

Azure Pricing Calculator: The Basics

The Azure Pricing Calculator is a tool that allows for:

• Estimating per month costs and extrapolating to annual cost estimates.

• Covers major Azure services and their various cost models.

• Allows for estimating temporary usage of resources – estimating autoscaling and/or other resources that are not provisioned 100% of the time.

• Tracking service usage across all regions, including AZUREGOV regions.

• Saving, exporting and sharing previously input values. This provides the capability to save progress, collaborate with other team members, and objectively evaluate changes to architecture or service consumption and the impact on cost.

Export, Save, Share capabilities

• Export generates a unique Excel file based on the resources defined within the calculator.

This file can be downloaded, modified, shared, etc.

• The Save feature captures the selected options to remain within an account for future use.

• Share generates a URL that can be used in the future or shared. This URL brings the user to a cost calculator prefilled with the resources and values previously saved.

Key points to remember when using the Pricing Calculator tool:

• The Azure Pricing Calculator is located at: https://azure.microsoft.com/en-us/pricing/calculator/

• Costs vary between regions – Ensure the appropriate region is selected: AzureGov (US Gov Virginia).

• Impact Level 5 systems are required to run on “AzureDOD” .The Azure Calculator does not currently support estimates for IL5. You can approximate costs using the AzureGovVirginia region.

• Ensure services being utilized or estimated are approved at the system’s Impact Level. The Cloud One Service Catalog is where services are defined at that various Impact Levels. The Cloud One Service Catalog is located at: https://intelshare.intelink.gov/sites/afcce/Pages/Service-Catalog.aspx

• Tool limitation to note: Azure Marketplace charges are not able to be estimated within the tool. To effectively estimate Azure Marketplace charges, the underlying Compute charges can be estimated using the tool, adding in additional Azure Marketplace charges outside of the tool.

https://azure.microsoft.com/en-us/pricing/calculator/ https://intelshare.intelink.gov/sites/afcce/Pages/Service-Catalog.aspx

Baseline Costs

Azure Pricing Calculator: Baseline Costs Overview

• Cloud One provisions several resources within every system’s AZURE Account. Cloud One maintains these services with no action required by the MSO. In the event these services are changed or updated in the future where there is a material impact on cost, MSO’s will be notified in advance so they can plan and budget accordingly.

• The services provisioned by the Cloud One team are:

• Bastion hosts

• Deployment Pipeline

• Azure Monitor

• Azure Security Center

• Azure Policies

• Azure Key Vault

Azure Pricing Calculator: Baseline Costs Overview

• Minor cost drivers:

• Azure Monitor

• Azure Security Center

• Azure Key Vault

• Major cost drivers:

• Bastion hosts

• Deployment Tooling

Not all of the Cloud One provisioned services are capable of being estimated in the Azure Cost Calculator.

The services missing from the calculator contribute in a minor way to overall cost. Therefore, the templates provided will only include the Major cost drivers.

To assist with estimations, the Cloud One baseline services are broken up into Major Cost Drivers and Minor Cost Drivers:

Azure Pricing Calculator: Baseline Costs

• Major Cost Drivers (Major Impact on Cost):

• Bastion hosts - Windows servers leveraged by the Common Gateway Service within Cloud One.

These are used for management traffic to securely access resources within the MSO’s account.

Estimated Cost: $350/month

• Deployment Pipeline– The tool used to execute automation code to deploy resources and systems within the MSO’s Azure account. This tool is leveraged by the MSO’s privileged management plane users while logged into the Bastion Hosts. Estimated Cost: $107/month

Azure Pricing Calculator: Baseline Costs

• Minor Cost Drivers (Minor Impact on Cost):

• Azure Monitor – which includes Log Analytics and Application Insights enables the user to utilize sophisticated tools for data gathering and analysis to maximize the performance and availability of cloud and on-premises resources and systems.

• Azure Security Center – this feature is a unified infrastructure security management system that provides advanced threat protection across hybrid workloads in the cloud as well as on premises.

• Azure Key Vault – Cloud services and systems use cryptographic keys and secrets to aide in keeping information secure. By utilizing the key vault feature it is possible to encrypt authentication keys, passwords, storage keys and more by using keys that are protected by hardware security modules.

• Azure Policy – this service enables users to create, assign, and manage policies. The policies aide in enforcing different rules and affect resources, which helps in staying compliant with operational mandates and service level agreements.

• For estimation purposes, the total cost of all these services is typically less than $100/month for Integration, Test and Production ($25/$25/$50).

Mission System Costs

Azure Cost Calculator: Mission System Costs Overview

Mission System Owners can provision a wide variety of services. Leveraging the Azure Cost Calculator, an MSO can accurately estimate annual costs. In this section, we will leverage the Cloud One Service Catalog and provide sample templates, considerations, and instructions for estimating the services.

Major Cost Drivers:

• App Service

• VMs (IaaS)

• SQL(PaaS)

• App Insights

• App Monitor

• Azure Event Hub

Minor Cost Drivers:

• Azure Service Bus

• LogicApps

• Standard Load Balancer

No Cost Services:

• Virtual Network

• Azure Resource Manager, VM Extensions, AzureAutomation

• AzureAD

• Azure Portal

Major Cost Driver: App Service and Cloud Services

App Service

• PaaS with the option to have your system hosted

3 different ways.

• Standard – 50Gb storage,5 staging slots, auto- scale up to 10 instances, SSL and Custom domain support.

• Premium – Faster vCores and RAM, 250Gb storage, 20 staging slots, auto-scale 20 instances, 50 backups per day.

• Isolated – Strong scaling, secure network access, high memory utilization and high initial cost.

Azure Pricing Template:

(https://azure.com/e/9511fbe41ca048beae96717840d14a42) https://azure.com/e/9511fbe41ca048beae96717840d14a42

Things to note on Azure Isolated Service Plan

• Flat usage fee of ~$1200 a month for the service.

• Up to 100 instances can be deployed of this system.

• Support Internal Load Balancer to segregate backend services from the internet

• Shares no resources with any other system

Key differentiators between App Services and Cloud Services is that Cloud Services provides access to the machine tied to it.

Within Cloud Services the system can be deployed in 1 of 2 roles. First is “Web Role” which hosts the App through IIS and the other role is “Worker Role” which runs the app through standalone.

The primary cost factors are the following:

• Instance Type: The type of compute resource you wish to deploy onto the Azure Cloud environment resource wise.

Major Cost Driver: VMs (IaaS)

AZVM estimate details:

• Instances: The number of instances with these settings to estimate.

• Usage: The amount of time these instances will be running. This field is most useful for estimating temporary resources and/or autoscaling. The options for units of measure include:

• % Utilized per Month

• Hours per Day

• Type: The Operating System type and the AZVM instance size. Within Azure’s VM offerings there are several specific isolated VM offerings for Impact Level 5 systems.

• Billing Option: On-Demand vs the various Reserved options and BYOL offer.

• Hours per Week

• Hours per Month

Major Cost Driver: Standalone Bastion Hosts

Operating Systems – For Windows machines licensing is included in the hourly pricing unless a license is provided.

Tier – Instances can be sorted and displayed depending on what type of workload you're expecting to perform.

Azure Pricing Template: (https://azure.com/e/ae15341dcb52401a845f3230c5b0a410) https://azure.com/e/ae15341dcb52401a845f3230c5b0a410

Major Cost Driver: Azure Managed Disks

Azure Managed Disk estimate details:

• Region: Defining which region you wish to deploy your azure disk storage.

• Types: What type of storage is required. This can be Managed Disk or an Unmanaged Disk.

• Tier : What type of disk is required. Can range from Standard HDD to a Standard/Premium SSD

• Disk Size: Amount of storage being provisioned for the specific disk.

• Number of Disks: Configure and decide how many Disks you wish to deploy with this specific configuration.

• Storage Transactions: Every instance that a storage block is accessed in Azure Storage it incurs a transaction cost. Premium SSD’s do not incur this.

• Snapshot Storage: The amount of storage expected to change and be saved in a snapshot during the month.

It is defined as the size of the possible snapshot multiplied per GB.

Major Cost Driver: Virtual Machine Scale Sets

There are no incremental charges for the Virtual Machine Scale Sets service itself.

Only the resources itself and the time of deployment.

In this example, we have 2 VM’s set to run 24x7 while the other VM’s are set to run only for 10 hours on business days only.

Azure Pricing Template: (https://azure.com/e/edc4757c2d9248aea280ac56abc85aed) https://azure.com/e/edc4757c2d9248aea280ac56abc85aed

Major Cost Driver: Azure Event Hubs

Key factors regarding pricing fore Azure Event Hub

• Ingress – Amount of events coming in to Event Hub that is billed per million events.

• Throughput Units – A single throughput unit is measured by Ingress and Egrees that are pre-purchased and billed per hour. Up to 20 units can be purchased under a EventHub Name space.

Azure provides a dedicated Event Hub service that is billed for $6,249.713 monthly that removes the ingress and egress restriction while also putting event hub into a single tenant.

Azure Pricing Template : (https://azure.com/e/a97d8b7b17c34c3282d0c0322e6b6454) https://azure.com/e/a97d8b7b17c34c3282d0c0322e6b6454

Major Cost Driver: Load Balancer

Standard Load Balancer cost estimates:

• Region: Region: Defining which region you wish to deploy your azure disk storage.

• Load Balancer rules: Create and define AZ Load Balancing rules. Price increases after 5 rules.

• NAT Rules: NAT defined rules are free of charge.

• Data Processed: Estimated amount of traffic that passes through the Load Balancer.

• Basic Load Balancer is free of charge.

Azure Pricing Template: (https://azure.com/e/43349d2930c947a4b3a131bcec31f527) https://azure.com/e/43349d2930c947a4b3a131bcec31f527

Major Cost Driver: Azure Storage/Virtual Disk

Azure Virtual Disk estimate details:

• Type: Azure Storage offers several types of storage accounts. Each type supports different features and has its own pricing model.

• Storage Account Type: Different storage account types fit different performance needs.

• Redundancy: Various replication offerings from local to geo-level based replication.

• Access Tier: Select the option depending on how often this resource is accessed.

• Capacity: Size of the storage

• Write/List/Create/Read Operations: Actions taken on the storage will incur a cost depending on the operation.

Azure Pricing Template:

(https://azure.com/e/6df8c05dfc324514a63c72e9a8f46bdf) https://azure.com/e/6df8c05dfc324514a63c72e9a8f46bdf

Major Cost Driver: Azure Storage - Blob

AZ Standard archive is a service used for archival purposes therefore data retrieval is not be expected to occur frequently. Azure’s cost is driven by how much data is being stored and the frequency of pulling data from it.

The following template is making an assumption that the data in Azure will need to be accessed once during the month via a standard retrieval request:

Azure Pricing Template:

(https://azure.com/e/98247e88bb3244ed83ec7c151f0d19f6) https://azure.com/e/98247e88bb3244ed83ec7c151f0d19f6

Major Cost Driver: Azure Storage - Archive

AZ Standard archive is a service used for archival purposes therefore data retrieval is not be expected to occur frequently. Azure’s cost is driven by how much data is being stored and the frequency of pulling data from it.

The following template is making an assumption that the data in Azure will need to be accessed once during the month via a standard retrieval request

Azure Pricing Template:

(https://azure.com/e/98247e88bb3244ed83ec7c151f0d19f6) https://azure.com/e/98247e88bb3244ed83ec7c151f0d19f6

Major Cost Driver: Azure Monitor

The pertinent fields for estimating Azure Monitor’s metrics are:

• Azure Resources: The number of services or instances collecting metrics.

• Alert Rules: The number of VM’s and metric’s being monitored for Metric’s and Logging.

• Frequency of metrics data: This is how often the custom metrics are measured. Azure provides this at 5/10/15 minute intervals.

• Notifications: This can be an E-Mail, push notification, web hook, phone call or text message.

Azure Pricing Template:

(https://azure.com/e/66f0f2f44a8041e5ba8d9fb0b901058e) https://azure.com/e/66f0f2f44a8041e5ba8d9fb0b901058e

Major Cost Driver: Azure Log Analytics The only relevant fields for estimating Azure Log Analytics costs are:

• VM Monitored: The number of VM’s having their logs ingested.

• Average logs ingested per VM (GB): The amount of new logs ingested into the Azure Log Analytics Service. The average Azure VM will ingest between 1-3 GB of data per month.

• Retention (Days * GB): The amount of additional days required to retain logs. Azure provides the first 31 days of retention free.

Azure Pricing Template: (https://azure.com/e/d216ba7dc54c45f09cecda4f63afe0b0) https://azure.com/e/d216ba7dc54c45f09cecda4f63afe0b0

Major Cost Driver: DBaaS for SQL

Azure SQL provides 3 different service models. Elastic Pooling, Single Database and Managed Instance*.

• Elastic Pooling provides scalability for systems during peak times. Its primary cost driver is the number of instances that are created

• Single Database is a SQL Database with its own set of resources and is managed via a SQL Database Server. Storage will be dynamically allocated based on ingestion.

• Managed Instance – Closest compatibility to SQL On- Prem; Includes SQL Agent; SQL Jobs

• An example template for a 512GB 8vCore SQL database can be found here:

(https://azure.com/e/414ced55f3d041f99b759c95b8da7577)

• An example template for a 2vCore 2 instance can be found here:

(https://azure.com/e/7c1814a12ed4412993b6c357d4033706)

• An example template for a 2vCore Single Instance DB can be found here:

(https://azure.com/e/86f8e6d98554445f8b0c12e31dfb7c96)

* Managed Instances on Azure Gov expected Q3 2019 https://azure.com/e/414ced55f3d041f99b759c95b8da7577 https://azure.com/e/7c1814a12ed4412993b6c357d4033706 https://azure.com/e/86f8e6d98554445f8b0c12e31dfb7c96

Major Cost Driver: Cosmo DB

In Azure Cosmos DB, you are billed for the provisioned throughput and consumed storage by the hour. Database account can also be configured to have all regions* to process the writes (multi-master) or exactly one region to process the writes (single-master).

Primary factors in determining cost:

• Storage: The size of the database

• Throughput: The throughput is expressed in terms of a normalized throughput currency called Request Units per second (RU/s). Once provisioned, RU/s can be used interchangeably across various database operations (e.g., inserts, reads, replaces, upserts, deletes, queries, etc.).

*CosmoDB pricing is not available in Gov Virginia. AZ Gov Arizona was used for the template

Azure Pricing Template: (https://azure.com/e/54cfbc9fc6bb4075bd7e3f9ee9996238) https://azure.com/e/54cfbc9fc6bb4075bd7e3f9ee9996238

Major Cost Driver: SQL Data Warehouse

SQL Data Ware House is built for intensive workloads and pricing is tied to utilization. For cost estimation Azure uses what is called “Data Warehouse Units (DWU)”. A DWU represents an abstract, normalized measure of compute resources and performance. Cost is primarily determined by this factor.

Here are the primary cost factors:

• DWU Blocks: Abstract unit for measuring compute needed for SQL.

• Storage: Azure defines their storage increments by the Terabyte starting from 1TB.

*SQL Data Warehouse pricing is not available in Gov Virginia. AZ Gov Texas was used for the example

Azure Pricing Template: (https://azure.com/e/5306b81d55e9449aa1f454bb80423a51) https://azure.com/e/5306b81d55e9449aa1f454bb80423a51

Minor Cost Driver: Azure Queue Storage

Azure Queue Storage is priced by two different Queue Class operations that are billed per 10,000 actions with Class 1 actions focusing more on creation of Queue’s and Data while Class 2 is focused on GET operations from the queue.

The primary cost factors are the following:

• Storage: The size of the Queue storage

• Queue Class Operations: Both operations are charged per 1*10,000 actions each. So 1 million requests would be 100 Operations * 10,000.

Azure Pricing Template: (https://azure.com/e/b73a651cf7fc40f8b662f834b3653050) https://azure.com/e/b73a651cf7fc40f8b662f834b3653050

Minor Cost Driver: Logic Apps

Azure’s Logic Apps is priced primarily against their basic and standard system integrations which can include Azure Service Bus and API management.

Pricing is primarily determined by

• The number of actions executed whether in a standard or enterprise connector.

• The number of integration accounts associated with the system.

Azure Pricing Template:

(https://azure.com/e/7417d2e6acd64ae5aa864d7e007d6d7c) https://azure.com/e/7417d2e6acd64ae5aa864d7e007d6d7c)

Azure Cost Calculator Predict and Optimize

Overview

In the previous section, the key cost factors for each service have been identified and templates have been included for the various services.

Now we will exercise these templates to forecast budget requirements and optimize our costs in real-world scenarios. This allows for the ability to:

• Forecast budgetary requirements

• Determine Impact of modifying system capability on cost

• Determine Impacts of modifications to system architecture on cost

As a part of determining the impacts of system architecture on cost, we will explore ways to optimize costs around required availability of particular services or when services have varying levels of usage. For example, implementing autoscaling in Production or stopping Integration or Test environments when they are not in use.

Analyzing an Invoice with Azure Calculator

In this example we examine the cost of two Redis Cache’s and compare their estimated price to the actual usage in a single billing period. Below you’ll find the usage for two SKU’s and that C1 had a near double amount of usage compared to SKU C5.

• With Azure Cost Calculator we are provided an estimate of the following. Comparing the two we found that the delta between the estimate from Azure Pricing calculator and invoice is $16.10. This can be understood easily as our C1 cache had a near double amount of utilization than the larger C5 Cache.

Azure Pricing Template: (https://azure.com/e/f7c9e0caae5547f383017d8664bfe5d2) https://azure.com/e/f7c9e0caae5547f383017d8664bfe5d2

Budget Forecasting for a System

As the system matures within the Cloud there are possible scenarios that an MSO should consider when forecasting budget for a system:

• Non-Autoscaling– All resources running 24x7x365 and no autoscaling being leveraged.

• Autoscaling the system - All resources running 24x7x365 with autoscaling enabled in Production.

• Optimizing the system – Minimum resources running in Production to maintain a highly available architecture. Autoscaling for peak demand is enabled in Production. Integration and Test environments are only running 8 hours per day.

• Adding new capability to the system requiring additional resources.

• Growing the system’s user base and estimating cost increases associated.

System Overview for Example Budget

Examining a near Non-Autoscaling migration into the cloud may be the first step for most system migrations.

Azure Prod/Test/Dev Environment:

• Max set of 4AZVM instances

• 100GB Disk Space Per Instance

• Azure LogAnalyticsmonitoring Metrics

• Azure LogAnalyticsand Metricsassigned to the VM

SQLRDS:

• Geo-Replication for Production DB

• Local Replication for Dev/Test (Business Hours only)

• Several GBof system artifactson Azure Blob Storage

• Azure LogAnalytics for system logs:

• 6 GBingested/month archiving for 1 year.

Azure Pricing Template: (https://azure.com/e/d3794900217045989deb1ef7ac16304d) https://azure.com/e/d3794900217045989deb1ef7ac16304d

Non-Autoscaling Budget Forecast

Reviewing the template for the Non-Autoscaling system, the monthly cost is estimated at $2,024.25/month. If this system is not expecting significant changes to usage or architecture over the next year, it can be an annual estimate of:

12 months * $1963.32 = $23,559.84 per year

Create the Cloud One Baseline Services total cost from the template found below https://azure.com/e/ce70b056d9684f4e8f6a7b9f4d35b6a6

12 months * [$2,522.13 ] = $30,265.56 per year

This gives a total annual budget estimate of a Non-Autoscaling system:

$30,265.56 + $23,559.84 = $53,825.4 per year https://azure.com/e/ce70b056d9684f4e8f6a7b9f4d35b6a6

Autoscaling the System Budget Forecast

Building upon “Non-Autoscaling System”, we will examine the impact on cost. What if, instead of provisioning for peak load, we built for autoscaling in Production?

The following are the required updates to the Non-Autoscaling estimate to change to Autoscaling:

• Remove the static cluster of 4 AZVM instances provisioned 24x7x365

• Replace with anAuto scale Group with a minimum size of 2 and a maximum of 4 instances – expecting the additional 2 instances to be running 12 hours per day.

Azure Pricing Template: (https://azure.com/e/56c8398526d846e0becb942bdd3c2907) https://azure.com/e/56c8398526d846e0becb942bdd3c2907

Autoscaling the System Budget Forecast

Reviewing the template for the auto scaled system, the monthly cost is estimated at $1,874.18/month. If this system is not expecting significant changes to usage or architecture over the next year, it can be an annual estimate of:

12 months * $1,874.18 = $22490.16 per year saving $1,069.68 per year

Create the Cloud One Baseline Services total cost from the template:

https://azure.com/e/3a8cdb376a3241ea92f49d45e9b86596

12 months * [$2,522.13 ] = $30,265.56 per year

This gives a total annual budget estimate of:

$22490.16 + $ 30,265.56 = $74,060.76 per year https://azure.com/e/3a8cdb376a3241ea92f49d45e9b86596

Optimizing the System Budget Forecast

Further building upon the Autoscaling system, we will examine the impact on cost if we turned off Iand Test resources outside of business hours.

Required updates to the Autoscaling estimate to further optimize around Dev and Test environments lower utilization levels:

• Update Dev & Test AZVM instances and SQLinstances to only run during regular business hours (8 hours per day)

Azure Pricing Template: (https://azure.com/e/0c0882358056425fb592235530c8b8f3) https://azure.com/e/0c0882358056425fb592235530c8b8f3

Optimizing the System Budget Forecast

Reviewing the template for the optimized system, the monthly cost is estimated at $936.04/month. If this system is not expecting significant changes to usage or architecture over the next year, it can be an annual estimate of:

12 months * $1299.81 = $15,597.72 per year saving $6892.44 per year

Create the Cloud One Baseline Services total cost from the template https://azure.com/e/3a8cdb376a3241ea92f49d45e9b86596

12 months * [$2,522.13 ] = $30,265.56 per year

This gives a total annual budget estimate of:

$15,597.72 + $30,265.56 = $45,863.28 per year

Adding New Capability Budget Forecast

Now that we have optimized the system, there is a target of a new capability that will require a new database. The targeted release is in approximately 6 months.

Required updates to the optimized estimate to add this new database:

• Add new SQLinstance for each environment

Azure Pricing Template: (https://azure.com/e/cc64d34fb7374fb9ba507b86ecac2b92) https://azure.com/e/cc64d34fb7374fb9ba507b86ecac2b92

Adding New Capability Budget Forecast

Reviewing the template for the optimized system, the new monthly cost is $2,093.88. Making the increase an estimated at $794.07/month for the new capability. If the capability is going to be released in 6 months, the increase required for the current Fiscal Year is: $2,525.76

The updated annual estimate of:

12 months * $2093.88 = $25,126.56 per year increasing by $4764.43

Now, create the Cloud One Services total cost from the template:

https://azure.com/e/3a8cdb376a3241ea92f49d45e9b86596

12 months * [$2,522.13 ] = $30,265.56 per year

This gives a total annual budget estimate of: $25,126.56 + $30,265.56 = $ 55392.12 per year

Adding Additional Users Budget Forecast

With the new capability launched, the user base is expected to grow by 50%. Performance testing has determined the system will need to scale out an additional 3 instances for 8 hours a day.

Required updates to the new capability estimate to accommodate the larger user base:

• Add 3 ProductionAZVM instances for 8 hours/day

• Add 3 additional disk volumesfor the new instances

Azure Pricing Template: (https://azure.com/e/f4a94db0c97d46bf931433392208d423) https://azure.com/e/f4a94db0c97d46bf931433392208d423

Adding Additional Users Budget Forecast

The updated annual estimate of:

12 months * $ 2,231.85 = $26782.2 per year increasing by $1655.64

Now, create the Cloud One Baseline Services total cost from the template:

https://azure.com/e/3a8cdb376a3241ea92f49d45e9b86596

12 months * [$2,522.13 ] = $30,265.56 per year

This gives a total annual budget estimate of:

$26782.2 + $30.265.65 = $ 57047.76 per year

Other Resources & Information

Monthly Invoices

If a system is running for longer than a month in Azure, the monthly invoice is a great tool for getting more detail into cost estimations. Noting the estimation templates and descriptions previously discussed, some metrics that are cost drivers may be difficult to estimate from an On-Prem perspective.

Once it exists, an actual invoice is a powerful tool. It provides specific numbers for each item that generates a cost for each service for each environment. Allowing MSOs to leverage the Azure pricing calculator more effectively and accurately using real data, as opposed to, estimated data.

Monthly invoices are delivered for MSOs at: https://intelshare.intelink.gov/sites/afcce/Invoices/Forms/AllItems.aspx https://intelshare.intelink.gov/sites/afcce/Invoices/Forms/AllItems.aspx

Current Pricing Details for Azure Services

Azure Service Pricing URL Azure Monitor https://azure.microsoft.com/en-us/pricing/details/monitor/

Azure Security Center https://azure.microsoft.com/en-us/pricing/details/security-center/

Azure Policy https://azure.microsoft.com/en-us/pricing/details/azure-policy/

Azure Key Vault https://azure.microsoft.com/en-us/pricing/details/key-vault/

Azure Resource Manager https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-overview

Azure Virtual Machine https://azure.microsoft.com/en-us/pricing/calculator/

Azure Storage https://azure.microsoft.com/en-us/pricing/details/storage/

Azure App Service https://azure.microsoft.com/en-us/pricing/details/app-service/windows/

Azure Storage Block Blob https://azure.microsoft.com/en-us/pricing/calculator/

SQL https://azure.microsoft.com/en-us/pricing/details/sql-database/single/

Azure Cosmos DB https://azure.microsoft.com/en-us/pricing/details/cosmos-db/

Azure SQL Data Warehouse https://azure.microsoft.com/en-us/pricing/details/sql-data-warehouse/gen2/

Azure Stream Analytics https://azure.microsoft.com/en-us/pricing/details/stream-analytics/

Azure Queues Storage https://azure.microsoft.com/en-us/pricing/details/storage/queues/

Azure Logic Apps https://azure.microsoft.com/en-us/pricing/details/logic-apps/ https://azure.microsoft.com/en-us/pricing/details/monitor/ https://azure.microsoft.com/en-us/pricing/details/security-center/ https://azure.microsoft.com/en-us/pricing/details/azure-policy/ https://azure.microsoft.com/en-us/pricing/details/key-vault/ https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-overview https://azure.microsoft.com/en-us/pricing/calculator/ https://azure.microsoft.com/en-us/pricing/details/storage/ https://azure.microsoft.com/en-us/pricing/details/app-service/windows/ https://azure.microsoft.com/en-us/pricing/calculator/ https://azure.microsoft.com/en-us/pricing/details/sql-database/single/ https://azure.microsoft.com/en-us/pricing/details/cosmos-db/ https://azure.microsoft.com/en-us/pricing/details/sql-data-warehouse/gen2/ https://azure.microsoft.com/en-us/pricing/details/stream-analytics/ https://azure.microsoft.com/en-us/pricing/details/storage/queues/ https://azure.microsoft.com/en-us/pricing/details/logic-apps/