![Microsoft Graph: New default passcode in the Create Meeting API [MC985483]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-picjumbo-com-55570-196645-1024x683.webp)
Message ID: MC985483
Before this retirement, when creating an online meeting using the Microsoft Graph API, admins or users can choose whether to require a passcode. If no value is specified, the default behavior does not require a passcode.
After this update: For enhanced security, users will still have the option to specify whether a passcode is required when creating a meeting. If no value is specified, the default behavior will require a passcode for the meeting.
Effective February 24, 2025, the default value of the isPasscodeRequired property will change from false to true.
Update your applications
Review and update any applications that use the Create onlineMeeting API and passcode to ensure they account for the new default behavior.
Looking ahead
In October 2027, we will remove the option to specify the need for passcodes. This change will ensure that all meetings are consistently secured with passcodes. This final step will simplify the meeting creation process and provide an additional layer of protection for users. We will remove the isPasscodeRequired property on the joinMeetingIdSettings resource of the Microsoft Graph online meetings API.
Source: Microsoft
![Power Apps – Update your firewall rules to add the new telemetry endpoints by February 20, 2025 [MC985408]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-steve-27366415-150x150.webp)
![Microsoft Teams: Additional work information in people search results [MC985484]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-punttim-139764-150x150.webp)
This update regarding the Microsoft Graph API’s new default passcode requirement is a significant shift that will impact both admins and users in notable ways.
For admins, the change means a proactive approach to security will be necessary. With the default setting shifting from not requiring a passcode to requiring one, administrators will need to review and potentially update their applications that utilize the Create onlineMeeting API. This is not just a minor tweak; it’s a call to action to ensure that all systems are aligned with the new security protocols. After all, who wants to be the admin that forgets to update their applications and ends up hosting an unprotected meeting? Talk about a virtual party gone wrong!
On the user side, this update introduces a layer of security that many will appreciate. While it may seem like an inconvenience to have to deal with passcodes, the reality is that it enhances the overall safety of online meetings. Imagine the peace of mind knowing that your meeting can’t be easily accessed by unauthorized participants. Plus, it’s a great excuse to make your friends and colleagues work a bit harder to join your next virtual gathering!
Looking ahead, the complete removal of the option to specify passcodes by October 2027 will further streamline the meeting creation process. This means less confusion and more time focusing on what truly matters: the content of the meetings themselves.
In summary, while there may be some initial adjustments for both admins and users, the long-term benefits of enhanced security and simplified processes are certainly worth it.
What do you think about these changes? Will they make your online meeting experience better, or do you foresee any challenges? Share your thoughts below and let’s discuss! For more insights and updates, feel free to check out additional posts on mwpro.co.uk.