Forum Discussion
Bookings not including audio dial-in
All of a sudden I have a Bookings site where their Teams meetings are not including audio dial-in information. Other Booking sites create the nice looking formatted Teams invite for the Staff, just like you'd see in a regular scheduled Teams meeting. This site is shows this horrible looking, almost plain text invite and it contains no dial-in information like your standard Teams meeting.
It's very odd. Anybody seen that before? It's not a licensing issue as all our users are licensed for Audio Conferencing. I'm at a loss as there doesn't seem to be any setting messed up.
carverberryMicrosoft
This is by design Microsoft booking invites do not include the dial in information in the ics files- Bumping this back up because it sounds like it is happening again (or maybe never got fixed) Our ICS files do not contain the dial-in information. Anybody else seeing this?
- Thank you for the bump. I'm experiencing this as well. Has anyone received communication from Microsoft about an anticipated resolution?
- I have been trying to get the dial-in information in the email confirmation or ICS file for over a year. I can't seem to find a solution. It does not matter if the appointment is booked from the back end of Microsoft Bookings Calendar or the public Bookings page. We pay for audio conferencing and the only time it shows up is if I book the appointment directly from Outlook. Any help would be appreciated.
- I am having the same issue. No Dial-in but only for Bookings. Regular meetings include the dial-in info.
- Hi - Microsoft has reverted the codes that caused the issue around noon yesterday. Should start to see issues resolved on new appointments, existing ones may still have issues.
- I've noticed that if I created appointments manually via the back-end, the appointment will include the dial-in # and the format of the invite is fine.
- Yep, it was happening from the bookings page. The booking page admin turned off the option to include a teams meeting, saved it, then turned it back on and it fixed itself until today when it is now happening again.
