Summary and Change description:

Schedule start: 29-June-21 15:00:00 pm IST

Schedule finish: 29-June-21 22:00:00 pm IST

Actual start: 29-June-21 15:00:00 pm IST

Autual finish: 29-June-21 22:00:00 pm IST

Name of Change request: Enable Yammer Community creation for Admins

Reason for Change: Yammer admins cannot create communities in Yammer, once Members of
O365_Yam_GroupCreators group is created the members of groups will be able to create Yammer
connected groups.

Current configuration:

1. Effect of not implementing: Business requirement will not be met.

2. Requested by: Malcolm Smith malcolm.smith@archerwell.com
3. Devices and/or servers (CI’s) in scope:
4. Environment: (PROD/TEST): Prod
5. Server Name(s) and role: NA
6. Affected users/sites/applications (Service Groups/Services):
7. Downtime ( outage related info): No
Downtime ( outage ) duration:NA
Downtime exact start and finish time, time zone: NA
8. End user impact: NO
Communication to end users?: No
9. Implementation Plan (incl. communication plan) :
Below are the steps to be performed by
Step1: Create a group for users who need to create Yammer connected groups.
Step 2: Run PowerShell commands

Contact details.-
IBM: Mohammed Sayeeduddin Afroz , shoaib.shaikh, Narmadha Palaniswamy,
sayeemoh@in.ibm.com, Narmadha.Palaniswamy@ibm.com; shoaib.shaikh@in.ibm.com
9703733302, 9148149918, 8939143867
Customer LITs contact details (if needed) : (name, mail, phone number)

10. Pretest details -

 Test plan (has the change been fully tested? (evidence) If not, please state reason):
Testing done through Office365 Support BAU
 Has it been considered if this implementation leads to changed needs in terms of
performance and / or capacity, and did you act upon this? – Yes, as we need to enable
Yammer couuminity creation for users who has Yammer Admin rights
 Has implementer verified the access(es) necessary to perform the change? - Yes
 Has necessary staffing been allocated and confirmed within all departments involved? - Yes
 Please confirm that systems monitoring will be informed of change start and end. Yes
 Carefully consider the length of the service window: Has sufficient time been estimated -
including time for fallback? Yes
 Observe the point of no return (Scheduled End minus Length of Fallback) to avoid exceeding
the service window: Yes

11. Verification Plan:

Note: Changes can take more thirty minutes or more to take effect. You can verify the
new settings by doing the following:
1. Sign into Microsoft 365 with a user account of someone who is member of
APP_GLOBAL_G_O365_Yam_Com_Creator and has Yammer permission.
2. login to yammer https://web.yammer.com/main/feed
3. In Yammer check if you can see the option to create community.
Note: If members of the group aren't able to create groups, check that they aren't being
blocked through their OWA mailbox policy.

1. Describe when the change should be verified: Change will be verified by Mohammed
Sayeeduddin Afroz after the change implementation on 29-June-21
2. Provide contact information - who will verify the change – Mohammed Sayeeduddin
Afroz , sayeemoh@in.ibm.com, 9703733302

12. Provide contact information - who will verify the change - Customer/user side (if N/A
provide reason): Malcolm Smith malcolm.smith@archerwell.com
3. !!! Please send email to the relevant Archer IT Lead (application owner/ Site lead) in case
of CI verification depended on client side.!!!

13. Fallback/Remediation Plan:

1. Test, has the fallback procedure been tested? If not, please state reason: Yes
2. Please describe how fall back should be executed (step by step):
Step 1: re-run the script to turn off the group creation restriction and again allow all
users to create groups, set $GroupName to "" and $AllowGroupCreation to "True" and
rerun the script
3. Please describe how successful fall back should be verified:
Mohammed Sayeeduddin Afroz , sayeemoh@in.ibm.com, will verify the successfull fall
back through Exchange Online PowerShell.
4. Please provide contact information - Who will be performing the fall back if necessary:
Mohammed Sayeeduddin Afroz , sayeemoh@in.ibm.com
5. Please provide contact information - Who will be verifying successful fall back:
Mohammed Sayeeduddin Afroz , sayeemoh@in.ibm.com
*************
14. In addition, for all exception changes, the change owner must ensure that a valid business
justification is provided in record using this template:
1. What will be the BUSINESS consequence if this exception change record is forced to
follow standard lead-times?
 2. When was the issue discovered by change requester (e.g. CIRATS open date/IM opened
time)?
3-June-21 12:00:00 pm IST
3. What is the latest possible schedule before IBM is hit by consequence mentioned?
This needs to be implemented on 29-June-21. Mentioned duration is adequate for
implementation and fall back if required.
**************

Scheduled Task information (exist separate schedule tab for these information): Not required
Each change should have at least one task with clear step by step implementation plan, information
of which team or teams will be performing the change
1. Consider Backup: No backup needed as there will be no data loss.
2. Please describe how to implement the change (step by step execution plan, including backup
procedures and maintenance mode if applicable):
3. Maintenance Mode (required or not) : Not required