.ics Calendar issue with Office 365

I’m properly set up. Appt does post to the phone. Phone just does not propagate the entry to the exchange cloud. Any other method of entering an appt on the phone works fine. And using the the .ics file to create the entry on my IPad (IOS 15) or desktop propagates properly to all devices including the phone, and I can than adjust or delete the appt on the phone and it changes on all devices. Been using my phone with my exchange account for years so I understand the process. Seems to be an IOS 16 glitch.

note that if I use Outlook for IPhone, works fine. Issue is only when I create the calendar entry in IPhones calendar app using an .ics file.

BTW, spoke to Microsoft. They said certain glitches are popping up between the native IPhone and Mail and Exchange, and recommended I start using the Outlook mail/calendar app. And that works fine, but I just don’t like the look and feel of the Oulook Iphone app on the phone. So for now, I’m using the Iphone native apps, but if I get an email with an .ics file, I take the extra step of opening it in the Iphone outlook app, create the calendar entry there( which creates it in the Iphone Outlook calendar) and it pops up on all devices including on the IPhone native calendar App

i don’t think you understand the issue, maybe did not explain clearly. Appt posts to the IPhone with no problem. However, the entry does not propagate to the cloud. So the appt is on the phone, but does not show up on my IPad, Desktop, or on line version of the exchange calendar. Manual addition of an appt. to the IPhone calendar works fine and transmits to the cloud. Entry propagates to the cloud and back down to all devices. If I use the .ics file to create the calendar entry on my desktop or IPad, the entry propagates to the cloud and back to all devices, including the IPhone. And once the entry has been created on the Desktop and propagates to the IPhone, I can then manipulate the entry on the phone (correct it, change time, or delete it) the change propagates to all devices. So the ONLY issue is that if I use the.ics file to CREATE the calendar entry on the IPhone, does not send the entry to the Exchange cloud. Every other function and every other calendar entry method works as it should. Not a problem if I use the .ics file to create the entry on my IPad running IOS 15, worked properly when I was running IOS 15 on the phone, so appears to be an IOS 16 glitch.

Note That I did delete and recreate the exchange account on the phone. Does not resolve the issue.

In case I'm not explaining this right, let me try a different way.

I open my Iphone native mail app. There is an email with an .ics file. I click on it, takes me to the IPhone calendar app, and I add the event. Call that Appt "A".

I then open the IPhone calendar app. Appt A is there. I then add a second appt for later in the day by hitting the + key . Call that Appt "B". So now, when I open my IPhone calendar app, both Appt A and Appt B are there. But if I go to my desktop calendar client, or to my IPad, Appt B is there, BUT APPT A (the one created by using the .ics file) IS NOT!.

If I go through the same sequence on my IPad, both Appt A and Appt B end up on my desktop, IPad, and IPhone! So everything works perfectly and as it should EXCEPT that the appt CREATED on my IPhone using the .ics file never leaves the IPhone to Exchange.

And again, if I create Appt A with the .ics file on my IPad, once it appears on my IPhone (and it does), and if I delete it on my IPhone, it deletes on my IPad and my desktop. The only thing that does not work is that an appointment created on my IPhone does not register to my Exchange account if the entry was created on my IPhone using an .ics file.

If I did not have the IPhone mail and calendar set up properly on the phone, Appt B would not propagate across all devices when I add it to my IPhone manually. Nor would deletion of Appt A on my IPhone (If I created it on my IPad or desktop using the same .ics file) delete the appt from my other devices. But it does!

Since Exchange is the only email account, the line to set the default account is not even there. But to test it, I added my Gmail account to the Iphone. That caused the line to set the default mail to appear. I set it to Exchange. I then went to Settings- Calendar and made sure my default calendar was also set to Exchange.

And same result. I click the .ics file, add it to my Iphone calendar, and it still does not post to my Desktop or IPad. Manually add another Appt to my Iphone Calendar, and the entry shows on both Desktop and IPad.

I don't use ICloud. When i reference "the cloud" I'm refering to the Exchange cloud, and only mention that so that you understand that if I go to my Exchange calendar on line it is not there either, which means the problem is not that the failure to propagate is in the transmission of data from Microsoft Exchange to my desktop client. The info never gets sent from the native IPhone App to Exchange, and I know that because if I check my Exchange calendar on line, it is not there.

Exchange works fine with Iphone mail and IPhone calendar so long as you set up the Exchange account in the IPhone. It has worked for me for years, and continues to work now with every mail and calendar entry on my IPhone other than an appointment created in the IPhone calendar from an .ics file contained in an email.

Keep in mind that if I access the email with the .ics from my IPad and click on the .ics file and create the calendar entry that way (using the Apple Mail and calendar apps), it works fine. Entry ends up on all my devices including the IPhone. The ONLY issue is that if the calendar entry is CREATED on the Iphone using an .ics file, the data never leaves the phone to go to Exchange. EVERY OTHER method of entering an appointment on the IPhone works as it should. And once the calendar entry is shown on the IPhone after creating it on my IPad or desktop, it shows up on the IPhone calendar app and changes made on my IPhone are transmitted properly to Exchange and my desktop and IPad. The ONLY issue (after extensive testing) is that when using one particular method to create the calendar entry (using an .ics file on the IPhone) that appointment does not transmit data to Exchange And it did until IOS 16. This is an IOS 16 glitch!