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.
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\
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
Run the RegisterBillingWithIdentitySystem.ps1 script with appropriate parameters
Go to Admin Portal -> Login as Service Admin -> Subscriptions -> Default Provider Subscription -> Check if role is Owner Eg: [email protected]
Azure Stack ARM endpoint. Eg: "https://adminmanagement.redmond.masi67.corp.contosotest.com/"
Azure Directory tenant Id
Cloud environment Eg: AzureCloud
Either "AzureAD" or "ADFS" depending on authentication mechanism used in the Azure Stack being added
Default Provider Administrator Subscription ID
PEP endpoint IP address
Cloud admin account user name
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)
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.