I researched this question a while back, when I was trying to auto-start Zoom meetings, and came up with a solution that would likely work to start Teams meetings as well.
I wrote a four-line Windows Powershell script that:
- launches Zoom
- waits a bit
- opens the URL for the Zoom meeting
- waits a bit
- closes the browser
(Newer browsers require a confirmation—they won't go right into the meeting—so I set the default browser to be an older version of Internet Explorer that will launch and join the meeting without confirmation.)
I also wrote a one-line Powershell script that quits Zoom, to end the meeting. (I have to "force quit" Zoom, because it wants a confirmation when quitting if there's an active meeting.)
After I wrote these, I used Task Scheduler to set up "Start Meeting" and "End Meeting" tasks that run the corresponding PowerShell scripts at the designated start and end times for the meetings.
(Each computer is set up to join the same meeting room for every meeting, but you could also write multiple "start meeting" scripts with different URLs.)
That's the solution I used for Zoom, and that's the setup I'm planning on using with Teams, once we start to migrate over.
UPDATE: Hmm... This works except for it still brings up the "audio and video settings" screen, with the Join Now button, for the "host", unattended computer. I'll have to add an "enter key" press to the "start meeting" PowerShell script, to enter the meeting.
Also, our host computers are Windows 10 machines, and this won't wotk on the Mac. The Office 365 apps are AppleScript-able, though, and you could likely write scripts that would launch meetings, press the "Join Now" button, and quit Teams, and have them execute at set times.
