Microsoft Teams bad request error? Here is a quick fix!

Microsoft Teams is a popular collaboration software for the organizations to help their team be on the same page. However, at times you may encounter several minor problems like Microsoft Team bad request error while trying to access a file or edit it.

The error can occur due to many reasons including permission issues. Many users have reported a similar error in the Microsoft tech forums.

Teams is up and running in our tenant but when I browse tohttps://teams.microsoft.com/it redirects tohttps://teams.microsoft.com/undefined/_and displays the text “Bad Request”. The client is working fine and the web portal was previously working fine too.

If you are also troubled by this error, here are a couple of troubleshooting tips to help you fix Microsoft Teams bad request error.

How to fix Microsoft Teams bad request error

1. Change Read Only Recommended Settings

1. The Microsoft Teams bad request error can occur if you have enabled the Read Only Recommended setting for the file.
2. Open the file in the native app. That is if it is a Word File, open the file in Microsoft Word.
3. Click on File > Saves As.
4. Click on Browser.
   
5. In the Save window, click on Tools and Select Generation Options.
   
6. Locate “Read Only Recommended” and uncheck the option.
7. Click OK and then save the file.
8. Go back to Microsoft Teams and then try to re-upload the file with the bad request error and check for any improvements.

2. Check the File Compatibility

1. The Microsoft Teams bad request error can also occur in case the file you are trying to access is not compatible with the current version of Microsoft Office app.
   
2. For example, if the file you are trying to edit is in .xls format or .doc format then try to change it to .xlsx and .docx format respectively.
3. Save the file in a new format and reupload the file in Microsoft Teams app.
4. The users should be able to access the file without any error this time.

3. Change the web browser

1. If you are trying to access the web client of Microsoft Teams, try changing the web browser to fix the error.
2. At times, the bad cache can create issues with the browser functionality for any specific URL.
3. If you are using Google Chrome, try accessing Microsoft Teams using Edge or Firefox. If the error is resolved after changing the browser, clear the browser cache to resolve the issue.

Another browser that you should try is UR Browser. This is privacy-focused browser built on Chromium engine.

The browser comes with built-in malware scanner for downloaded files, adblocker, tracking protection, and a built-in VPN, so it will be a perfect choice if you want to secure your privacy while browsing the web.

UR Browser is a great alternative to Chrome. Read our in-depth review to find out why!

Clear Browser Cache for Chrome

1. Click the Menu icon and select Settings.
2. Click on Advanced to expand the section.
3. Scroll down to Security and Privacy section.
   
4. Click on the “Clear browsing data” option.
5. Select a time range and then check ” Cookies and other site data” and “Cached images and files” option.
6. Click the Clear Data button.
7. Relaunch Chrome and check if the error is resolved.

If the issue persists, try to check Microsoft Teams Dekstop client for any pending update and install it.

1. Click on the Files tab
2. Click on Get link
3. Now, click on the SharePoint tab and copy the respective link.
4. Paste the link you just copied in the file name section on the save screen.

• Does Microsoft Teams have version control?

Microsoft Teams supports file and document version control but it is not stored directly on the platform.

Here are the steps to follow to access the version control file:

1. In Microsoft Teams, go to the Files page and select the document you want to open
2. Click on the option that allows you to open it SharePoint
3. The SharePoint library should now appear on the screen
4. Locate the document you’re interested in
5. Scroll down to version history and check the first version of the document

[wl_navigator]