Update default value for AllowEngagementReport #9629
Conversation
The default value for AllowEngagementReport is Enabled if no value is specified when the Teams meeting policy is created from PowerShell.
|
Docs Build status updates of commit c05afa8: ✅ Validation status: passed
For more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
|
@dariomws @get-itips @tseward |
|
Hello @robertpp Robert
|
dariomws
left a comment
dariomws
left a comment
There was a problem hiding this comment.
Agree with @get-itips, we saw this before.
|
Hi @get-itips , thanks for the information, I wasn't aware of it. I confirm seeing the same behavior in our tenant, but totally missed the Global policy was no longer set to the default. This should be reflected in the documentation, as it is confusing, especially since the TAC behavior is different. I would suggest the following changes: |
|
Hello @robertpp how are you? the default value in the Global policy is not disabled, it's just that in my lab I changed it to disabled. We can't put this Matches (value in) Global policy for Default value field as it is expecting a value or None, the general convention is using None when the value can not be exactly determined as it depends on Global policy/current settings in customer tenant. I think we should leave this article as-is. Thank you! |
|
@robertpp Please comment. |
|
Thank you for the comment @get-itips . I understand now the reason for None. The documentation says the meeting attendance reports download is off by default, which to me it means the default value in the Global policy is turned off.
The confusion starts when AllowEngagementReport in the Global policy is turned on. To prevent false expectations, it might be worth indicating the dependency on the value of AllowEngagementReport in the Global policy for subsequent policies. |
|
It seems that sentence is outdated as the linked article says
On new tenants, in the global policy, it appears to be on by default. So I think the article requiring an edit is the one you linked that says it is off by default. About this one, a note can be added that the initial values of the new policy are copied from the Global one. |
|
Hi @get-itips . Thank you for the feedback. I raised another item for the other article. It's surprising to learn that it is enabled by default in Global policy. The entire documentation, including internal, except the article you mentioned, indicates it is off by default for privacy reasons. I even have a case where the customer is complaining about the feature not being compliant with GDPR. That's how I got to raise these items. Your efforts and clarifications are much appreciated. |
|
@dariomws can you check on your tenants? |
|
@get-itips @robertpp, it's enabled in my demo tenant, it should be the default value for the Global policy. |
|
Thank you for confirmation, @dariomws . |
|
@robertpp Robert, sorry, on my opinion, I was more inclined to leave "None" as value.
@dariomws thoughts? |
|
Agree with @get-itips. |
|
@robertpp Please comment |
|
Hello @yogkumgit and @tiburd . Apologies for the slow follow up. I was on vacation the past 2 weeks. I agree with @get-itips' suggestion. |
|
@robertpp Thank you and no worries. I am closing it. |
7 participants
The default value for AllowEngagementReport is Enabled if no value is specified when the Teams meeting policy is created from PowerShell. This is the opposite of what happens when a new meeting policy is created in Teams admin center.