question

That particular limit is for the number of times a single Key/Value pair in user data can be updated in 15 seconds. That means that need to update the exact same value with extreme frequency, so I'd recommend having a look at our pricing page: https://playfab.com/pricing/. While I understand you're in our Indie tier right now, you should be designing for the new pricing model, since your title will be using it once the grace period has elapsed (so, by October 1st). Writing to player data at that frequency is going to be a very significant cost, so you'll want to either a) find ways to aggregate the data over longer periods of time, or b) use a custom game server to host the state information for the game for the player, so that you can update the backend (long-term) store of data less often.

That said, if you're already aware of this and your monetization is designed to account for higher than normal costs per player, you can reach out to our sales team via sales@playfab.com to get information on potential costs for a private cluster of PlayFab in which we could enable higher limits based on your specific needs.

The same would apply to the other limits, though for Cloud Script we would recommend updating to use the newer Azure Functions Cloud Script, in which you can have longer-running scripts that use more API endpoints by making them queued functions.