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 have the same issue and also opened an MS Case #2502281410000431
best regards
My case is #2502260040008631. My tech support person was able to reproduce what is going on with the calendar. It looks like they may be working on it because now when you open the calendar although it is still starting with 1899, there is a Today button now that actually takes you to "today".
We are also having issues with Outlook on web calendar when you try to share your calendar using "share calendar". The links are not working for the invitee. I was told although this is related have to create another support case which I am also doing this morning.
I still do not understand the fear/hesitancy of posting this in Service Health (first place I go before researching any M365 issues).
My ticket is #2502100030001010, which I reported 2 and a half weeks ago. They tell me that they have had other reports. But it is frustrating that it is taking a long time.
Appreciate the information, thanks!
Agreed it is frustrating that it is taking so long, and that there isn't something listed under Service Health to document this problem.
For anyone else that has the ability to open MS Support tickets, I would suggest opening tickets and referencing the support numbers listed in this thread to hopefully raise visibility.
For anyone that has opened a ticket with Microsoft Support, please provide your case number. I just opened case #2502280040000098 and they have reported that they are not able to see other reports. It may get more attention if we can pool these support tickets together.
Thanks.
Strange!
As I mentioned, I cant guarantee that our fix works for others. But for us it works really good.
/Henric