The "Last saved" relative time-stamp on a search, alert or alert plan appears to be inaccurate (4224132)

Consider the following scenario:

1. A new shared type search, alert or alert plan is created
2. The relative time-stamp in the UI states: "Last saved in a few seconds by user1@domain.com"

The expected outcome for the relative time-stamp scenario above would be:

"Last saved a few seconds ago by user1@domain.com"

The time settings are not synchronized properly on the host where the browser is running. In other words, the time on the host computer is off (in this example it is behind a few seconds) when compared to the accurate time in Azure. This causes the relative time statement to suggest the search is created in the future ("in a few seconds" in the example used here).

Ensure the host time settings are configured correctly.

Note: The absolute time-stamps in the informational tool-tip will reflect the correct times even in the scenario where the host/browser time is not properly synchronized.