Added "View in File Explorer" - it works in SharePoint but not Teams for all libraries

Question

Added "View in File Explorer" - it works in SharePoint but not Teams for all libraries

Frank Becker 0

Having followed the instructions here to enable "View SharePoint files with File Explorer in Microsoft Edge" - https://learn.microsoft.com/en-us/SharePoint/sharepoint-view-in-edge -- AND IT WORKS AS DESCRIBED! (Thank you Microsoft, we have many users that are happy to see this functionality return) However - we find that the "View in File Explorer" library view appears BOTH in SharePoint for all the document libraries, and in the Teams view options for all libraries -- From SharePoint, it works as designed - However - Even though the "View in File Explorer" option also appears within the Teams /files\ tab - Both for the Teams App and Teams Web View (using Edge) - selecting this option in Teams either does nothing, or displays a red circle/slash as if security has not been allowed - My guess is, we need to tell Edge to trust credentials from Teams (like we had to tell it to trust SharePoint - in the configuration instructions at the earlier part of my note here) is there a secondary policy setting we need to add? Yes, selecting from Teams to first "Open in SharePoint" then choosing this option is the current work-around, but since the option exists directly in Teams, it would be optimal to get it working from there directly.

1 answer

Your answer

Answer 1

Rin-L 10,005 Microsoft External Staff Moderator

Hi @Frank Becker,

Thank you for posting your question in the Microsoft Q&A forum.

Based on my research, the issue you're experiencing is likely due to the ConfigureViewInFileExplorer policy being set only for the SharePoint domain, and not for the Teams domain.

The root cause is that your current ConfigureViewInFileExplorer policy may only be configured for sharepoint.com or your organization’s specific SharePoint domain. However, Microsoft Teams uses the domain teams.microsoft.com to access files. When you click "View in File Explorer" from Teams, Edge is not permitted to open WebDAV URLs from this domain.

Please try updating the ConfigureViewInFileExplorer policy to include the Teams domain as well. Change the policy value from:

[{"cookies": ["rtFa", "FedAuth"], "domain": "sharepoint.com"}]

to:

[ 
  {"cookies": ["rtFa", "FedAuth"], "domain": "sharepoint.com"}, 
  {"cookies": ["rtFa", "FedAuth"], "domain": "teams.microsoft.com"} 
]

After making the change, restart Microsoft Edge and verify that the policy has been applied by visiting edge://policy.

Note: Please allow 15–20 minutes for the changes to take effect.

If you get stuck at any step or have any additional questions during the process, please feel free to leave a comment under this post. I’ll be happy to assist you further.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Frank Becker 0 Reputation points

2025-09-15T15:52:21.1366667+00:00

@Rin-L thanks for your suggestion - we deduced the same last week and tried adding it on Friday- same result (it does not work yet) - as we dug through the page in developer view, we do see the following message:

Access to fetch at 'https://consumer.entitlement.skype.com/users/self/services' from origin 'https://teams.microsoft.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.

So - we are wondering if it would help or harm if we add this 3rd url "consumer.entitlement.skype.com" to the policy value? Or if this is not really related to the issue.
Rin-L 10,005 Reputation points Microsoft External Staff Moderator

2025-09-16T10:20:21.9166667+00:00
Hi @Frank Becker,

Thank you for your follow-up.

Regarding the CORS error with consumer.entitlement.skype.com, this is expected behavior and does not require any intervention. It does not resolve or impact the “View in File Explorer” functionality. In fact, attempting to bypass this error could introduce unnecessary security implications.

Based on my research, the ConfigureViewInFileExplorer feature in Microsoft Edge is designed to allow the browser to pass WebDAV commands (via the viewinfileexplorer: scheme) from trusted SharePoint Online pages to Windows File Explorer. While Teams does display the “View in File Explorer” button, it actually triggers an API request (not a WebDAV call) from teams.microsoft.com to consumer.entitlement.skype.com, which is blocked due to CORS restrictions.

Edge policies cannot force the server to include the necessary headers to bypass CORS, so there is no client-side configuration that can resolve this.

Additionally, there is currently no official Microsoft documentation that supports enabling “View in File Explorer” directly within Teams (desktop or web). All official guidance related to ConfigureViewInFileExplorer is found in:

View SharePoint files with File Explorer in Microsoft Edge - SharePoint in Microsoft 365 | Microsof…

Microsoft Edge Browser Policy Documentation ConfigureViewInFileExplorer | Microsoft Learn

The currently approach is to use “Open in SharePoint” from within Teams, and then select “View in File Explorer” from the trusted SharePoint page.

That said, I truly appreciate your suggestion. It’s a valuable idea that highlights a real usability gap. However, as a forum moderator, I hope you understand that I do not have the ability to escalate or modify product features directly. So, I strongly encourage you to submit this as a feature request via the Microsoft Teams · Community

This is the official portal where your input goes directly to the product team and can be considered for future improvements.

Here’s a sample message you can use or adapt:

Subject: Feature Request - Native "View in File Explorer" Support in Microsoft Teams Hello Microsoft Teams Product Team, I would greatly appreciate a native feature in Microsoft Teams that allows users to open SharePoint/Teams document libraries directly in File Explorer without needing to first open SharePoint in the browser. Enabling this feature would improve usability and efficiency for many users managing files in Teams. Thank you for considering this enhancement.

Once you've posted your feedback, feel free to share the link in the comments here. I’ll be happy to vote for it to help bring more visibility. In the meantime, I’ll also do my best to raise awareness of this issue internally.

If my response has helped clarify the situation and guide you toward a possible next step, please consider marking it as the “Accepted Answer.” This will pin the post to the top and make it easier for others in the community who have similar questions or ideas to find it.

Thank you again for your precious time!
Rin-L 10,005 Reputation points Microsoft External Staff Moderator

2025-09-17T09:06:37.0833333+00:00

Hi @Frank Becker,

I hope you're having a great day!

Is there any update from you? If yes, please feel free to let me know.

Looking forward to hearing from you!
Rin-L 10,005 Reputation points Microsoft External Staff Moderator

2025-09-18T07:39:40.22+00:00

Hi @Frank Becker,

I hope this message finds you well.

This is my second follow-up to check whether your issue has been resolved. I truly want to ensure your experience is as smooth as possible. If your problem is still ongoing or if you have faced any new difficulties, please share more details about the current steps you are stuck on. I am here and happy to provide further help whenever you need it.

While waiting for your response, I will continue tracking other customer questions on the forum to ensure everyone receives timely support. If you have additional questions, please feel free to tag my name in your reply so I can assist you promptly and more personally.

Looking forward to hearing from you soon.

Share via

Added "View in File Explorer" - it works in SharePoint but not Teams for all libraries

1 answer

Your answer