Outlook Calendar Status Automator

[joker3000]

Outlook Calendar Status Automator​

https://github.com/joker3000/outlook365-calendar-status-automator​

Project Purpose​

This tool was built for office employees using a 3CX phone system integrated with Microsoft 365, who:

• Have automatic calendar integration enabled in 3CX (via Microsoft Graph)
• Appear “busy” in 3CX during any Outlook appointment – even personal or self-created ones
• Want to remain available for phone calls despite having personal calendar events

By converting self-created busy events to “free”, users can:

• Keep their calendars intact
• Avoid call redirection or DND status in 3CX
• Maintain full control over availability for telephony

 

[Evolute IT]

We have presence sync now which is even better.

 

[joker3000]

Interesting. Please tell me more about it. Are there some docs or references available?

 

[Evolute IT]

Seriously?

https://www.3cx.com/docs/manual/microsoft-365/

 

[joker3000]

Seriously?

https://www.3cx.com/docs/manual/microsoft-365/

This is mainly meant to be used if MS Teams is not established in a company.

 

[Evolute IT]

This is mainly meant to be used if MS Teams is not established in a company.

There's the old calendar sync that still works if enabled.

 

[joker3000]

That is basically correct. However, Outlook sets a booked status by default in a new calendar entry which is “busy” and is therefore also treated as such by default in 3CX. This tool provides a remedy by keeping the agents accessible for 3CX again by default in this specific use case with an M365 integration.

 

[Evolute IT]

That is basically correct. However, Outlook sets a booked status by default in a new calendar entry which is “busy” and is therefore also treated as such by default in 3CX. This tool provides a remedy by keeping the agents accessible for 3CX again by default in this specific use case with an M365 integration.

Or teach users to use the different modes in Outlook's calendar.

 

[joker3000]

I agree, but an initial integration requires a one-off adjustment. Thanks for your input so far.