Hi @dutta_pitam , which version of IIQ that you using “I’ll assume 8.4“
Simple answer for O365 groups, yes you can
Teams and Yammer are just layers on top of that… Teams usually works via the same Unified group, while Yammer remains largely outside of the connector, except where it already uses an M365 group in the background.
Note: this is based on my understanding and knowledge, please validate and here you are the official docs…
Have a nice and great one!
Regards,
Mustafa
@Muhammad_Mustafa : Thanks for your response. I was able to create M365 groups of Types Planner and Teams directly from SailPoint while for Yammer the approach was a bit different as i had to call Yammer specific graph API’s to create the community which is generally not supported from OOTB Entra connector.
Hi Pitam,
The documentation does come up short on the details of Teams creation.
Here is an example of Team creation:
ObjectRequest or = new ObjectRequest();
or.setOp(ProvisioningPlan.ObjectOperation.Create);
or.setApplication("Azure");
or.setType("group");
or.add(new AttributeRequest("displayName", name));
or.add(new AttributeRequest("description", description));
or.setInstance(name); // needed to prevent the PlanCompiler from merging object requests
or.add(new AttributeRequest("mailNickname", "msteams_" + Long.toString(mailNicknameSequence++)));
or.add(new AttributeRequest("groupTypes", "Office365"));
or.add(new AttributeRequest("visibility", "HiddenMembership"));
or.add(new AttributeRequest("teamsEnabled", Boolean.TRUE));
or.add(new AttributeRequest("addOwnerAsMember", Boolean.TRUE));
// creationOptions (if specified) must have more than one value to avoid conversion to a scalar
or.add(new AttributeRequest("creationOptions", Arrays.asList("ExchangeProvisioningFlags:461", "classAssignments")));
or.add(new AttributeRequest("extension_fe2174665583431c953114ff7268b7b3_Education_ObjectType", "Section"));
or.add(new AttributeRequest("resourceBehaviorOptions", Arrays.asList("HideGroupInOutlook", "WelcomeEmailDisabled")));
or.add(new AttributeRequest("owners", owner));
@dutta_pitam Glad that you find the way, and thanks for sharing the result as well ![]()
