发布SaaS解决方案并处理第三部分API帐单. [英] Publishing SaaS solution and handling 3rd Part API billing.
问题描述
我已经开发了内部Azure解决方案，我希望将其发布为SaaS产品.该解决方案调用具有基于消费的计费方式的第三方API.
I've developed an inhouse Azure solution that I am looking to publish as a SaaS offering. The solution calls 3rd party APIs that have their own consuption-based billing.
根据文档，我的解决方案必须有一个固定的每月价格.
According to the docs, my solution has to have one fixed monthly price.
支付第三者费用的最佳/允许方式是什么?
What is the best / allowed way to cover the 3rd party cost?
- 按月收费，这笔费用涵盖了潜在的消费，这使我的服务变得昂贵，因此没有吸引力.
- 根据估计的消费量和实物支付的风险，按月收费.
- 让我的客户直接与第三方建立他们自己的帐户，然后创建和修改解决方案以允许他们输入API密钥，从而增加设置的复杂性.
- 与第三方对话，以期引起轰动交易.
关于消耗，我们如何计算月度费用，因为Azure的费用基于1.或2.起作用的使用情况.我特别在考虑如何在多租户解决方案中分配Azure成本.
On the subject of consuption, how do we go about working out the monthly charge as Azure's charges are based on usage where 1. or 2. come into play. I'm specifically thinking about how Azure costs are split in multi-tenancy solutions.
TIA
推荐答案
For questions related to billing, log a ticket with Microsoft Support here.
--------------------------------------------------- -------------------------------------------------- ----------------------------------
如果此答案有帮助，请单击"标记为答案"，然后单击投票.要提供有关您的论坛体验的其他反馈，请单击
这里
-----------------------------------------------------------------------------------------------------------------------------------
If this answer was helpful, click "Mark as Answer" and Up-Vote. To provide additional feedback on your forum experience, click
here
这篇关于发布SaaS解决方案并处理第三部分API帐单.的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
