Azure Stack Hub Billing
Cloud Assert HomeDocs Home
2105.2
2105.2
  • Introduction
  • Release Notes
  • Features
    • Cost Management Across Multiple Azure Stack Hub Stamps
      • Connecting to an Azure AD Stamp
      • Connecting to an ADFS Stamp
    • Admin Features
      • Settings
      • Pricing Profile
        • Manage Pricing Profiles
      • Usage History
      • Invoice
      • Quotas
      • Credits
        • User Credits
      • Usage & Quota
      • Notifications
      • Health Status
      • Billing Subscriptions
      • Enabling End Users To View Usage Costs And Quota Consumption For Subscriptions Across Stamps
    • Tenant Features
      • Overview
      • Usage History
      • Invoice
      • Notifications
      • Usage and Quota
      • Billing Profile Creation
      • Manage Subscriptions
  • Installation
    • Prerequisites
      • PKI Certificate Requirements
      • Azure Stack Certification Authority certificate
    • Deployment
      • Install Billing Resource Provider
        • High Availability and Scale Deployment considerations
      • Operations and Monitoring
      • Billing Database and Log File Configuration
      • License Activation
      • Update VConnect Resource Provider With Billing Details
    • Configuration
      • Setup pricing profile and quotas
      • Invoice
      • Add Billing service to Azure Stack Plan
      • Add the resource provider in Tenant Portal
      • Mapping Subscriptions
      • Billing Tool Command Reference
    • Version Update
    • Remove Resource Provider
Powered by GitBook
On this page
  • HOST VM OF THE STAMP TO BE CONFIGURED
  • Billing Resource Provider VM

Was this helpful?

  1. Features
  2. Cost Management Across Multiple Azure Stack Hub Stamps

Connecting to an ADFS Stamp

HOST VM OF THE STAMP TO BE CONFIGURED

On AzS Development Kits, sign in to the physical host.

On multi-node integrated systems, the host must be a system that can access admin end point.

  1. Place the RegisterBillingWithIdentitySystem.ps1 file in a temp folder. This file can be found in the install folder of Host VM where Billing resource provider was installed: c:\CloudAssert\BillingRP\BillingApp\

  2. Open a new elevated (administrative) PowerShell console and change to the above directory. Use a new window to avoid problems that might arise from incorrect PowerShell modules that are already loaded on the system

  3. Run the RegisterBillingWithIdentitySystem.ps1 script with appropriate parameters

.\RegisterBillingWithIdentitySystem.ps1 -ServiceAdminUser '' -AzureStackAdminResourceManagerEndpoint '' -AzureDirectoryTenantId '' -AzureEnvironment 'AzureCloud' -IdentitySystemType 'ADFS' -PrivilegedEndpoint '192.168.200.224' -CloudAdminUser '' -adminSubscriptionId ''

Eg:
.\RegisterBillingWithIdentitySystem.ps1 -ServiceAdminUser 'msmtest@cloudassertrp.contoso.com' -AzureStackAdminResourceManagerEndpoint 'https://adminmanagement.local.contoso.com' -AzureDirectoryTenantId  'eef3d6b3-cf97-42c1-9cc5-f68905cdd1a6' -AzureEnvironment 'AzureCloud' -IdentitySystemType 'ADFS' - PrivilegedEndpoint ‘191.168.200.224’ -CloudAdminUser 'cloudadmin@azurestack.local' -adminSubscriptionId 'a7f2bc5b-2287-4a8b-b256-dcb14dd06878'

Parameter Name

Description

Required

ServiceAdminUser

Go to Admin Portal -> Login as Service Admin -> Subscriptions -> Default Provider Subscription -> Check if role is Owner Eg: admin@contosotest.onmicrosoft.com.

Required

AzureStackAdmin

ResourceManager

Endpoint

Azure Stack ARM endpoint. Eg: "https://adminmanagement.redmond.masi67.corp.contosotest.com/"

Required

AzureDirectory

TenantId

Azure Directory tenant Id

Required

AzureEnvironment

Cloud environment Eg: AzureCloud

Required

IdentitySystemType

Either "AzureAD" or "ADFS" depending on authentication mechanism used in the Azure Stack being added

Required

AdminSubscriptionId

Default Provider Administrator Subscription ID

Required

PrivilegedEndpoint

PEP endpoint IP address

Required

CloudAdminUser

Cloud admin account user name

Required

Billing Resource Provider VM

To support certificate authentication, import the .pfx file generated in the above step into Billing resource provider VM. Ensure the certificate is imported into the Personal store of this VM.

PreviousConnecting to an Azure AD StampNextAdmin Features

Last updated 3 years ago

Was this helpful?

The script outputs BillingRegistrationOutput.txt in the same folder having all the information needed to add a new azure stack connection in Billing using the billing tool command. (Refer: )

Connection with Certificate Thumbprint