Yes, this may be usefull for your environment. the Cloud witness as quorum would help to identify the appropiate availability depending on the region in case of nodes down in one region.
For reference I would just mention the Cloud Witness article: https://learn.microsoft.com/en-us/windows-server/failover-clustering/deploy-cloud-witness
In general, Whether the cluster continues running depends on how many nodes are online in the other regions—the remaining nodes need a majority of votes in the cluster quorum, which could be tricky if you have two nodes + the cloud witness go down together, but with 4 Nodes you can ensure resilience and reliability to the structure.
Here is an example of four nodes plus a witness: https://learn.microsoft.com/en-us/azure-stack/hci/concepts/quorum#four-nodes-with-a-witness
• In this example, if you had two nodes + the witness go offline, the cluster would go down because the remaining two nodes have 2/5 of the votes, which doesn’t comprise a majority.
• I’m thinking in this kind of scenario, you might want to put the cloud witness in a different region than the primary region so it can act in its intended role as an external tiebreaker.
Hope this helps with your query,
--
--If the reply is helpful, please Upvote and Accept as answer--