I've got a somewhat similar problem.
I have a Google Calendar set up at work, because it syncs nicely with the company-issued phones and is shared with my boss.
This calendar gets updated frequently because meeting are adjusted, for instance.
I subscribed to this ical calendar, with my win8.1 laptop, to be notified and never miss a meeting with my boss.
Now the problem is, the refresh interval for a subscribed calendar is so long it never updates in time. To get the expected notifications, I had to install chrome who provides me updates. I like the win8.1 calendar app, so I wish, as the original poster
did, to adjust the refresh interval to my calendar, to keep it in sync.
As the original poster, I expect more from Microsoft than providing us a calendar app that is basically designed to never show an up-to date calendar.
Also, I'm sure you'll understand that due to the purpose of the subscribed calendar, I cannot share the link with anyone outside my company.
However, you can easily reproduce our issue.
- set up a Google calendar,
- subscribe to it from oulook.com (since it's not possible to do it from the calendar app itself, which is surprising in the first place)
- set an event in a few hours on your Google calendar.
- get back to work.
- at the end of the work day, see on your windows app that the event (probably) still doesn't show on your windows calendar app. neither do it appear on your outlook.com webapp. neither did you receive any notification on your screen.
- if you apply this to a regular business situation, yell in anger and shame about that meeting you just missed.
BONUS STEPS.
- to try to force refresh, unsubscribe and subscribe again to the calendar.
- be amazed that the event STILL DOES NOT APPEAR.
- wonder and guess that instead of actually reading the link when subscribing, the outlook.com server stores your data without warning, presumably to prevent downloading the same .ics files multiple times.
Is that clear enough ? will you please either 1) relay this issue to the outlook.com team so that they adjust their data-storing policy, or 2) relay this issue to the calendar team so that they can patch the app to directly subscribe to a calendar ?