Microsoft 365 and Office | Install, redeem, activate | For home | Other
Processes in Microsoft 365 for setting up Office apps, redeeming product keys, and activating licenses.
In the netherlands this problem is also solved
Why is our published Outlook calendar showing as 1899 in our website
![](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)
Anonymous
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?
Microsoft 365 and Office | Install, redeem, activate | For home | Other
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.
53 answers
Sort by: Oldest
-
Anonymous
2025-03-04T14:30:33+00:00 -
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
-
Anonymous
2025-03-06T13:20:21+00:00 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).
It seems to be working here in Switzerland. Thanks for the fix.