Processes in Microsoft 365 for setting up Office apps, redeeming product keys, and activating licenses.
We should all just switch to using Google calendars... if only that didn't require shifting the platform that our whole organization uses.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Our outlook calendar looks fine in outlook but the shared link (html) that we use on our website is showing the calendar as 1899. We have not made any changes to our website so can only assume Microsoft has made some kind of update that has caused this?. How do we rectify or get Microsoft to resolve the issue?
If you click on Today then that takes you to the view that users should be seeing but obviously our users will not know to do that (and why should they)
Just to add to this, if you copy the shared html link from outlook and paste into the browser, the issue is replicated without going via our website so the issue looks likely to be a Microsoft Outlook one?
Processes in Microsoft 365 for setting up Office apps, redeeming product keys, and activating licenses.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
We should all just switch to using Google calendars... if only that didn't require shifting the platform that our whole organization uses.
As a temporary measure we added a JavaScript that reloads the Iframe after 3 seconds and most browsers load the current date then. It requires that your Iframe have an ID attribute.
[removed_js] { const iframe = document.getElementById('yourIframeId'); // Replace 'yourIframeId' if (iframe) { iframe.src = iframe.src; }}, 3000);
I just find it ridiculous that this is taking so long to fix. This group is probably just a small section of the people affected and while its not a show stopper its causing impact probably to thousands if not millions of people!!
Appreciate you confirming that we're not alone in experiencing this! I wish there was a way to get a quick solution to this - tough because I am pretty sure the issue is on Microsoft's end.
Hello?? Microsoft? Is there a solution to this that is being worked on? Again, pretty sure it is an issue with the internal time zone or clock or something like that.
Just spent an hour with Microsoft trying to find a realistic work around for the mean time. He couldn't figure anything out but mentioned they're aware of the issue as there are other tickets submitted with the same problem.