How to or What's the best method to keep a "staging" wordpress site that is in sync with production? So we can test updates.

Did you look at Preview environments in Azure Static Web Apps?

By default, when you deploy a site to Azure Static Web Apps each pull request deploys a preview version of your site available through a temporary URL. This version of the site allows you to review changes before merging pull requests. Once the pull request (PR) is closed, the temporary environment disappears.

Melven Atillo , could you please share more details/requirement? Are you leveraging Azure App Service or Azure Static Webapps.

Adding to Rick's response, if you are leveraging Azure App Service, it allows you to create staging slots. This feature lets you deploy your WordPress site to a staging environment that mirrors your production site. You can test updates in the staging slot before swapping it with the production slot.

Depending on the requirement, you may try the following approaches:

Development and Testing: You can have separate slots for development, staging, and testing your web app without affecting the production environment. This allows you to validate changes before making them live.

Blue-Green Deployments: You can set up a production slot and a staging slot. When you're ready to release a new version, you can swap the slots, making the staging slot the new production slot. This enables zero-downtime deployments.

You may take a look at the article by one of colleague, which outlines steps for setting such a requirement for WordPress on App Service: How to set up staging slots in WordPress on App Service

For more info: Staging environment with WordPress on App Service

Kindly let us know, we will follow-up with you further.