For the platform to collect Subscriptions with quota type EA ,CSP, or MCA, one of the following has to be true:

1. The Subscription has reader role permissions - In this case, we will collect the Subscription and all it's assets through our API collection process
2. The Subscription has costs and is present in the bill - In this case, we will derive the Subscription from the bill into the CloudHealth platform

For the platform to collect Subscriptions with quota PayAsYouGo (GAYG), the Subscription has to have reader role permissions since it will get derived from the bill - In this case, we will collect the Subscription and all it's assets through our API collection process. 

For more information on how to assign a Billing Reader or Reader roles to Subscriptions, see:

For Pay As You Go: https://docs.vmware.com/en/VMware-Tanzu-CloudHealth/SaaS/getting-started-with-vmware-tanzu-cloudhealth/GUID-azure-quick-start.html#step-2--add-reader-role-for-subscriptions-14

For EA: https://docs.vmware.com/en/VMware-Tanzu-CloudHealth/SaaS/getting-started-with-vmware-tanzu-cloudhealth/GUID-azure-quick-start.html#step-3--add-reader-role-for-subscriptions-5 

For MCA: https://docs.vmware.com/en/VMware-Tanzu-CloudHealth/SaaS/getting-started-with-vmware-tanzu-cloudhealth/GUID-azure-quick-start.html#step-2--add-reader-role-for-subscriptions-21