OfficeDocs-SkypeForBusiness
OfficeDocs-SkypeForBusiness copied to clipboard
MicrosoftDocs
Inconsistency in the Engagement report doc
The Engagement report default value is Off. This is mentioned in the notes of View and download meeting attendance reports in Teams and in Microsoft Teams meeting attendance report. The option is turned off when a new Teams meeting policy is created from Teams admin portal, but Enabled when a new Teams meeting policy is created in PowerShell.
Thank you for the review, @JohanFreelancer9. I'm not sure I'm doing it right, as I only have the 'Close pull request' button available.
@CarolynRowe PR has been copyedited and is ready for final review, could you please check and merge? Thanks!
There is a problem with this PR. The change is inconsistent with the paragraph following the change. @robertpp Can you please clarify?
Proposed change says the policy is off by default: This policy is off by default. If you turn this on, your organizers can see who registered and attended the meetings and webinars they set up. To turn it on in the Teams admin center, go to Meetings > Meeting policies, and set the Engagement report setting to Turn on.
But two paragraphs down still says the parameter is Enabled by default.
By default, the AllowEngagementReport parameter is set to Enabled in PowerShell. To prevent a meeting organizer from downloading the meeting attendance report, set the AllowEngagementReport parameter to Disabled.
If the following is true, then we need to clarify. Because current change request doesn't clarify the following: The option is turned off when a new Teams meeting policy is created from Teams admin portal, but Enabled when a new Teams meeting policy is created in PowerShell. I would also follow up with the PMs. Is this the expected behavior?
Hello @CarolynRowe . This request was due to an incorrect understanding on my side based on incomplete information and erroneous assumptions. There are more details about this on another request.
In summary, the policy is no longer off by default in the Global policy. According to the references mentioned in the first post and internal documentation, this was supposed to be off by default, due to privacy concerns. Something must have changed on how PG regards this feature.
There is also a dependency between the AllowEngagementReport value in the Global policy and the AllowEngagementReport in new meeting policies. All new policies follow the setting in the Global policy if not set. This is not documented anywhere and became the scope of the second GitHub item.
Finally, I made a confusion regarding the 'Turn on' visible in TAC when a new meeting policy is created. I interpreted it as an option to turn on the feature, meaning it is currently turned off, when it actually means the feature is turned on. Probably the best here would be to change 'Turn on' with 'Enabled' and 'Turn off' with 'Disabled', which would match the PS implementation and would prevent confusions, but this is not within the scope of this request.
To conclude, the actual purpose of this item remains alignment of the public documentation with respect to the actual default value of the policy. It turns out the needed change is to update the 2 references in the first post, which continue to state the default is off. At least one of them should probably mention also why such default is not regarded as a concern for privacy, since such default might raise a brow with our GDPR-compliant customers.