This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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 are in Australia, and we are definitely experiencing the issue here. Hopefully the development team should be able to see that from the tickets that it is a global issue.
We are in Australia, and we are definitely experiencing the issue here. Hopefully the development team should be able to see that from the tickets that it is a global issue.
Ahh thanks for clarifying this (the agent had tested from the Perth time zone of UTC+8 in case that is different than your region). Otherwise it could be then that the problem doesn't exhibit itself from inside MS networks.
But hopefully they have enough information by now to fix this promptly.
A few updates:
All of the cases referenced above have been linked to a single engineering request.
The engineering team has confirmed it's a global issue.
As I understand it, they plan to deploy it out globally some time today.
Many thanks for this update, fingers crossed on the fix!!
A few updates:
All of the cases referenced above have been linked to a single engineering request.
The engineering team has confirmed it's a global issue.
As I understand it, they plan to deploy it out globally some time today.
FYI it is working for us now in our testing (California, North America).