שתף דרך

Deploy-FinOpsHub command

The Deploy-FinOpsHub command either creates a new or updates an existing FinOps hub instance by deploying an Azure Resource Manager deployment template. The FinOps hub template is downloaded from GitHub. To learn more about the template, see the FinOps hub template.

Deploy-FinOpsHub calls Initialize-FinOpsHubDeployment before deploying the template.


Syntax

Deploy-FinOpsHub `
    -Name <string> `
    -ResourceGroup <string> `
    -Location <string> `
    [-Version <string>] `
    [-Preview] `
    [-StorageSku <string>] `
    [-RemoteHubStorageUri <string>] `
    [-RemoteHubStorageKey <string>] `
    [-Tags <object>] `
    [<CommonParameters>]

Parameters

Name Description
‑Name Required. Name of the FinOps hub instance.
‑ResourceGroup Required. Name of the resource group to deploy to. It gets created if it doesn't exist.
‑Location Required. Azure location to execute the deployment from.
‑Version Optional. Version of the FinOps hub template to use. Default = "latest".
‑Preview Optional. Indicates that preview releases should also be included. Default = false.
‑StorageSku Optional. Storage account SKU. Premium_LRS = Lowest cost, Premium_ZRS = High availability. Note Standard SKUs aren't available for Data Lake gen2 storage. Default = "Premium_LRS".
‑RemoteHubStorageUri Optional. Data Lake storage endpoint from the remote hub storage account. Used for cross-tenant cost data collection scenarios. Example: https://primaryhub.dfs.core.windows.net/
‑RemoteHubStorageKey Optional. Storage account access key for the remote hub. Used for cross-tenant cost data collection scenarios. Must be kept secure as it provides full storage access.
‑Tags Optional. Tags for all resources.

Examples

The following examples demonstrate how to use the Deploy-FinOpsHub command to deploy or update a FinOps hub instance.

Deploy latest version

Deploy-FinOpsHub `
    -Name MyHub `
    -ResourceGroup MyNewResourceGroup `
    -Location westus

Deploys a FinOps hub instance named MyHub to the MyNewResourceGroup resource group. If the resource group doesn't exist, it gets created. If the hub already exists, it gets updated to the latest version.

Deploy specific version

Deploy-FinOpsHub `
    -Name MyHub `
    -ResourceGroup MyExistingResourceGroup `
    -Location westus `
    -Version 0.1.1

Deploys a FinOps hub instance named MyHub to the MyExistingResourceGroup resource group using version 0.1.1 of the template. This version is required for Microsoft Online Services Agreement (MOSA) subscriptions since FOCUS exports aren't available from Cost Management. If the resource group doesn't exist, it gets created. If the hub already exists, it gets updated to version 0.1.1.

Deploy with remote hub configuration

Deploy-FinOpsHub `
    -Name MyRemoteHub `
    -ResourceGroup MyRemoteHubResourceGroup `
    -Location westus `
    -RemoteHubStorageUri "https://centralfinooshub123.dfs.core.windows.net/" `
    -RemoteHubStorageKey "abc123...xyz789=="

Deploys a FinOps hub instance named MyRemoteHub configured to send data to a remote (central) hub. The remote hub storage URI and key enable cross-tenant data collection scenarios where a central tenant aggregates cost data from multiple tenants. The RemoteHubStorageUri should be copied from the central hub's storage account Settings > Endpoints > Data Lake storage, and the RemoteHubStorageKey should be copied from Security + networking > Access keys. Remote hubs require template version 0.4 or later.


Give feedback

Let us know how we're doing with a quick review. We use these reviews to improve and expand FinOps tools and resources.

Give feedback

If you're looking for something specific, vote for an existing or create a new idea. Share ideas with others to get more votes. We focus on ideas with the most votes.

Vote on or suggest ideas


Related content

Related solutions:


  • Last updated on