Yes. Since every customer tends to have a different type of payment systems that they use, we defer the customer to have choice of their payment system and we just provide integration with it.
We will work with you to understand the best way to integrate with your choice of payment system and we will create mechanisms to accomplish the integration. If the integration requires lot of custom work, then we will add it to the deployment cost and you will know firsthand how much the total solution will cost.
Precisely because every customer has different way to collect payments, this solution doesn’t involve the real payment collection instead it builds on top of Azure Pack constructs and integrates with existing payment systems. For example, if you disable a user in your billing system, say WHMCS for any reason such as payment not received, this solution can automatically disable the subscription in Azure Pack, however this solution itself doesn’t track payments etc.
Yes. You can run plan-level promotions that are recurring or valid for a specific number of days. You can also offer hourly credits for metered resources, or offer credits per user.
Once the unit price is changed in the pricing profile, the usage cost for the records will take effective only for records that are newly generated. It would take a minimum time of 2 hours (in case of VMs) to a maximum time of 48 hours (in-case of Databases). Note: For existing records the newly set unit price will not take effective.
Yes, you can. Change the unit price of a meter resource in a pricing profile and follow the steps in Run Reset Usage (1). It will take about three to ten minutes to generate the records with the newly set unit price.
Yes, it is possible to set price for meters that are not listed by WAP. Visit the following link to know more.
The usage in the tenant portal updates every 60 seconds. It is also depending on the Resource providers that you have. For example, Systemcenter VMs update the usage record every two hours and SQLServers update usage records every two days in the WAP database. Usage and Billing solution checks for the usage records every 60 seconds and updates in the tenant portal after computing the usage cost.
By default, AppPool identity will suffice.
The API credentials are used for registering the U&B API service in WAP. It doesn’t have to be a valid user account it can be any username and password.
If the WAP URLs change, then they need to be updated appropriately under the WAP Admin Portal Usage & Billing Settings section (across WAP Usage, WAP Admin API tabs). If Usage & Billing is setup in same machines where WAP admin components exist, then Usage & Billing API Service URL will also change, so you need to update the U&B resource provider configurations using PowerShell API. Refer to this article.
Usage and billing - resource provider settings needs to be updated accordingly in tenant config file. Refer to Step 4 – Configuring Tenant Site .
It can be any user name and password. There are no conventions and it is not a local computer user account. It is a user account which will be used to access the WAP Usage component which is running in WAP.
It can be done by using runbook scripts which will suspend the subscription (with and without shutting down the VM) and prevent Network access when it meets the criteria(quota).
It is already reported in GB. You could change the custom formula to report it in MB/KB/GB. The below is the formula for reporting the same in GB. (The meters for network usage are ‘*NICKBSentPerSecond-Average’ and ‘*NICKBReceivedPerSecond-Average’).