[New resource] TeamsProtectionPolicy

[ykuijs]

Pull Request (PR) description

This PR adds a new resource for TeamsProtectionPolicy

This Pull Request (PR) fixes the following issues

• Fixes TeamsProtectionPolicy: New resource proposal #5296

Task list

• Added an entry to the change log under the Unreleased section of the file CHANGELOG.md.
  Entry should say what was changed and how that affects users (if applicable), and
  reference the issue being resolved (if applicable).
• Resource parameter descriptions added/updated in the schema.mof.
• Resource documentation added/updated in README.md.
• Resource settings.json file contains all required permissions.
• Examples appropriately added/updated.
• Unit tests added/updated.
• New/changed code adheres to DSC Community Style Guidelines.

[ricmestre]

@ykuijs I understand why you called it TeamsProtectionPolicy but this is actually an EXO resource, I think it should be renamed to maybe EXOTeamsProtectionPolicy.

[ykuijs]

@ykuijs I understand why you called it TeamsProtectionPolicy but this is actually an EXO resource, I think it should be renamed to maybe EXOTeamsProtectionPolicy.

That was something I was thinking about as well when developing. We have to connect to ExchangeOnline and change the setting there, but the setting is for Teams.......I chose to name it Teams since it is really meant for Teams.

@NikCharlebois, what is your opinion on this?

[ricmestre]

I use separate app registrations for each workload and they have their separate API permissions/roles, it will be hard to justify my customers which have EXO and Teams workloads why they will need to have one EXO admin for EXO and another one for Teams just because of a single resource.

[ykuijs]

True, depends from which angle you look at it. From a management perspective it is confusing that if you want to manage Teams, you have to use Teams resources and a single EXO resource.

[ykuijs]

Just checked with Nik. There are more resources like this, where we are following the underlying API in the naming. Will update this resource as well to match the EXO naming.