Open nikki-c opened 2 years ago
Sounds good @nikki-c
How do you see this working in the Power App? A simple Yes/No for needing review?
We'll need to work out if the policy is set to selected Teams as you say, as a flag in the settings list? That an admin will have to manually update.
Thoughts?
@alexc-MSFT How I have it working now in is that the user answers a question such as is this a project/ short term or operational/department team. Or the user selects a team template such as Project, Event, Department team. If it is a project/short term/ event then add the Expiration policy that has already been set up in the Azure AD Admin portal.
At the moment you can only have one Expiration policy so it need to be a yes/ no decision.
If using based on Team templates it needs another column added to the Team template SharePoint list. Expiration Policy with a Y/N option.
Allow a user when requesting a team to decide if it need to be added to the Azure AD Group expiration policy or not.
So for example : an operational team that does not need reviewing but a project based team would need reviewing. Note the pre requisite is that the Azure AD Group Expiration policy is enabled and the option is set to selected Teams. and not all Teams.
This is actioned using the Graph API: Group Lifecycle policy POST https://graph.microsoft.com/v1.0/groupLifecyclePolicies/{id}/addGroup Content-type: application/json Content-length: 57