Hi, All
While I don't think I can suggest a solution to your problem, I do think I can help with clarifying some things I noticed in this thread.
First, SCORM courses are built to run from a SCORM conformant LMS. Even if you get your courses to launch directly from Teams by targeting the INDEX.HTML file, they're not likely going to behave the way you probably hope. NOTE: a lot of this will depend on how the courses were built; i.e., what authoring tool or framework was used.
But generally speaking, because SCORM is meant to facilitate communication between courseware and LMS, the courses are likely to be filled with code that wants to regularly check-in with the LMS, to do things like record which page the learner is on, or what responses they provided to questions, etc. Each time your learner does something that the course wants to record these SCORM calls will be triggered, and without an LMS to receive and respond it's pretty likely they'll see communication error messages (if those are built into the courseware) or just find themself unable to proceed while the course waits to hear back from the LMS.
With all that said, these are generalizations, and it certainly is possible to build a SCORM course that has the ability to recognize when it's not being delivered via LMS and to silence the SCORM communications. I just wouldn't automatically expect that behavior unless you specifically accounted for it when building the courseware.
Also, as mentioned by another respondent, you definitely need to unzip the SCORM packages before you'll see anything at all. Your browser can't run HTML, Javascript, etc. from inside a zip file. But even if you do unzip the SCORM packages, I still wouldn't expect the courses to function in any useful way without an LMS, or SOME sort of SCORM engine to deal with the SCORM calls back and forth... unless your courseware has the kind of logic I mentioned earlier to run "off LMS".
I know this isn't a solution, but I do hope it's helpful.
Good luck!