A gaming company is building a global player profile service. Player state (inventory, scores, session data) is stored as JSON documents and must be readable and writable with single-digit millisecond latency from any of five Azure regions. The application can tolerate reading data that is a few seconds stale in exchange for higher availability during regional issues, but the same document must never be seen going backward in time by a given client session. Which storage solution and configuration should you recommend?