-
Notifications
You must be signed in to change notification settings - Fork 513
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pinning Copilot for non-licensed users #11764
Comments
Hi KurupatiC! Thank you for bringing this issue to our attention. We will investigate and if we require further information we will reach out in one business day. Please use this link to escalate if you don't get replies. Best regards, Teams Platform |
@KurupatiC - Thank you for bringing this to our attention! We will get the document updated to add above mentioned point. |
Hello! |
@Meghana-MSFT can you please let us know the article will be change? Although a minor change, customer is counting on this and since it is regarding Copilot, please prioritize. We need to provide an significant updato to customer - can you please help us with this? |
We are checking this internally, we will get back to you. |
Type of issue
Typo
Feedback
Cx is looking for public information of current documentation for pinning Copilot in Teams to be updated.
We know that Copilot will not appear as pinned for users who don't have a Copilot license, as this was changed earlier in the year based on customer requests.
However, we also know that as per Wave2 Copilot enhancements the tenant setting will honor the pinning of Copilot icon to Teams and other M365 apps. Cx followed this article and wants the information that pinning will not happen for non-licensed users to be added, as this is not made clear:
https://learn.microsoft.com/en-us/copilot/microsoft-365/pin-copilot
Page URL
https://learn.microsoft.com/en-us/copilot/microsoft-365/pin-copilot
Content source URL
https://github.com/MicrosoftDocs/microsoft-365-docs/blob/public/copilot/pin-copilot.md
Author
@surbhigupta
Document Id
4bbe9beb-233f-cfd5-097b-f280aab5fde8
The text was updated successfully, but these errors were encountered: