microsoft-teams-apps-requestateam VS Microsoft365DSC

If I were you I would trust users to organize themselves (i.e. don't restrict their ability to create teams too much, ...), that way people can adapt the platform to their needs. If you need more control over Team creation there's also the Request a Team app.

I'm new to Power Automate but followed a few guides and can bulk create Teams/add owner from an Excel sheet and a basic "Request a Team via a list/form". I do plan on implementing the "RequestATeam" app from the OfficeDev Github: https://github.com/OfficeDev/microsoft-teams-apps-requestateam

Or MS' own DSC solution!

M365 DSC documentation has a list of 'resource list' at https://github.com/microsoft/Microsoft365DSC/wiki/Resources-List but this list does not translate to a few modules we have: Defender for Identity, Power BI, Azure information protection, Defender for cloud apps, defender for O365. Are these M365 components/features supported by M365 DSC, if so under which resources? are there any gotcha's when trying to use DSC to export the config and use it on another tenant?

Microsoft365DSC is an Open-Source initiative hosted on GitHub, lead by Microsoft engineers and maintained by the community. It allows you to write a definition for how your Microsoft 365 tenant should be configured, automate the deployment of that configuration, and ensures the monitoring of the defined configuration, notifying and acting on detected configuration drifts. It also allows you to extract a full-fidelity configuration out of any existing Microsoft 365 tenant. The tool covers all major Microsoft 365 workloads such as Exchange Online, Teams, Power Platforms, SharePoint and Security and Compliance.

Links about: https://microsoft365dsc.com/ https://github.com/microsoft/Microsoft365DSC DSC Community Microsoft 365 Virtual Marathon - Microsoft365DSC, The next best thing since sliced bread

If handling CUI (CMMC ML3 or higher), you'll need to demonstrate practice and process maturity, take a look at Microsoft365DSC https://github.com/Microsoft/Microsoft365DSC. Combination of detective controls to implement: generate alerts if the configuration that requires encryption changes/generate logs providing positive verification that the configuration is in place; perform automated audits of the configuration on a regular schedule to validate that the configuration is in place. In both cases, retain the evidence (log files, alerts, DSC exports, etc.) so assessors can see that the configuration has been in place and that oversight is continuous and proactive.

Use https://github.com/microsoft/Microsoft365DSC to capture your environment or making changes to it to, commit to a public repository and add to your resume.