Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Known issues that are no longer known issues #3686

Merged
merged 4 commits into from
Jan 8, 2020
Merged

Known issues that are no longer known issues #3686

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
c2fb211
Known issues that are no longer known issues
marcoscheel Dec 21, 2019
c763137
Add another no longer known issue
marcoscheel Dec 21, 2019
be219e2
Removed another issue
marcoscheel Dec 22, 2019
bdbeeeb
Merge branch 'live' into patch-2
LolaJacobsen Jan 8, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 1 addition & 32 deletions Teams/Known-issues.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,12 +24,6 @@ This article lists the known issues for Microsoft Teams, by feature area.

## Administration



|**Issue title**|**Behavior / Symptom**|**Known workaround**|**Discovery date**|
|:-----|:-----|:-----|:-----|
|Audit logs may report an incorrect username as initiator when someone has been removed from a Team <br/> |Teams team is a modern group in AAD. When you add/remove a member through the Teams user interface, the flow knows exactly which user initiated the change, and the Audit log reflects the correct info. However, if a user adds/removes a member through AAD, the change is synced to the Teams backend without telling Teams who initiated the action. Microsoft Teams picks the first owner of team as the initiator, which is eventually reflected in the Audit log as well. <br/> | <br/> |5/11/18 <br/> |

|**Issue title**|**Behavior / Symptom**|**Known workaround**|**Discovery date**|
|:-----|:-----|:-----|:-----|
|EAF policy in the Enhanced Mitigation Experience Toolkit (EMET) can incorrectly identify Chromium sandbox optimizations as threats. <br/> |There is an issue with Chromium sandbox in which the Export Address Table Access Filtering (EAF) policy in the Enhanced Mitigation Experience Toolkit (EMET) and in Windows Defender Advanced Threat Protection (ATP) can incorrectly identify Chromium sandbox optimizations as threats. This causes Teams to not work properly. <br/> | To work around this issue turn off EAF for Teams. You can read more about the issue [EMET mitigations guidelines](https://support.microsoft.com/en-us/help/2909257/emet-mitigations-guidelines) For more information about Windows Defender ATP and EAF policy, see [Enable exploit protection](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/enable-exploit-protection) <br/> |10/11/18 <br/> |
Expand All @@ -56,10 +50,6 @@ This article lists the known issues for Microsoft Teams, by feature area.
|:-----|:-----|:-----|:-----|
|"Assignments" app remains visible when disabled <br/> |When the "Assignments" app is disabled in the admin center, it remains visible within the Teams client for EDU-licensed users. Selecting it when disabled will return an error indicating, "Doh! Something went wrong..." <br/> |No workaround. <br/> |12/29/17 <br/> |

|**Issue title**|**Behavior / Symptom**|**Known workaround**|**Discovery date**|
|:-----|:-----|:-----|:-----|
|Unable to delete connectors as a team owner <br/> |Attempting to delete a connector as an owner, that can otherwise add a connector, while "Allow members to create, update, and remove connectors" is disabled throws an error indicating the user does not have permission to do so. <br/> |Temporarily enabling "Allow members to create, update, and remove connectors" will allow the owner to delete the connector. <br/> |7/27/18 <br/> |

## Audio Conferencing

|**Issue**|**Behavior/Symptoms**|**Known workaround**|**Discovery date**|
Expand Down Expand Up @@ -133,8 +123,6 @@ This article lists the known issues for Microsoft Teams, by feature area.

## Client



|**Issue title**|**Behavior / Symptom**|**Known workaround**|**Discovery date**|
|:-----|:-----|:-----|:-----|
|Can't start Teams for Surface Hub from Microsoft Store |Microsoft Teams for Surface Hub won't start when you click **Launch** in the Microsoft Store. | Launching the Teams for Surface Hub app from the Microsoft Store listing isn't supported by Windows on Surface Hub. <br> <br/> Please restart your Surface Hub after installing Teams. | 2/27/18 |
Expand Down Expand Up @@ -163,10 +151,6 @@ This article lists the known issues for Microsoft Teams, by feature area.
|:-----|:-----|:-----|:-----|
|EU and APAC customers receive an error when they add a guest user from another tenant <br/> | Customers in EU and APAC experience a replication delay between Microsoft Teams and Azure Active Directory. When a user from an EU or APAC tenant tries to add a guest user from any other tenant, they receive an error message asking them to try again. <br/> |Click the retry button again to execute the addition of the guest user. <br/> |11/8/17 <br/> |

|**Issue title**|**Behavior / Symptom**|**Known workaround**|**Discovery date**|
|:-----|:-----|:-----|:-----|
|Wiki not created for channels created by guests <br/> |When a guest creates a new channel, the **Wiki** tab is not created. There isn't a way to manually attach a **Wiki** tab to the channel. <br/> |No workaround. <br/> |9/20/17 <br/>|

## Linux

|**Issue title**|**Behavior / Symptom**|**Known workaround**|**Discovery date**|
Expand Down Expand Up @@ -242,10 +226,6 @@ This article lists the known issues for Microsoft Teams, by feature area.
|:-----|:-----|:-----|:-----|
|Users might not be able to switch accounts on Intune-managed mobile devices <br/> |Users might not be able to switch accounts on Intune-managed mobile devices. <br/> |No workaround. <br/> |9/20/17 <br/>|

|**Issue title**|**Behavior / Symptom**|**Known workaround**|**Discovery date**|
|:-----|:-----|:-----|:-----|
|Mobile Client Teams Layout differences <br/> |Teams are listed in alphabetical order and the channels can't be collapsed on the mobile client. <br/> |No workaround. <br/> |3/13/17 <br/>|

|**Issue title**|**Behavior / Symptom**|**Known workaround**|**Discovery date**|
|:-----|:-----|:-----|:-----|
|Issues you may encounter if using iOS 13 Beta <br/> |1. Teams notifications are not being fired. This includes chats, mentions, and calls. 2. File preview is not working with the beta build. <br/> |At this time there is no workaround. We are working with Apple developers to find fixes for these issues. <br/> | 6/25/19 <br/>|
Expand Down Expand Up @@ -348,11 +328,8 @@ This article lists the known issues for Microsoft Teams, by feature area.

|**Issue title**|**Behavior / Symptom**|**Known workaround**|**Discovery date**|
|:-----|:-----|:-----|:-----|
|Audit logs may report an incorrect username as initiator when someone has been removed from a Team <br/> |Teams team is a modern group in AAD. When you add/remove a member through the Teams user interface, the flow knows exactly which user initiated the change, and the Audit log reflects the correct info. However, if a user adds/removes a member through AAD, the change is synced to the Teams backend without telling Teams who initiated the action. Microsoft Teams picks the first owner of team as the initiator, which is eventually reflected in the Audit log as well. <br/> | <br/> |5/11/18 <br/> |
|Teams voicemail emails will arrive with spf fail if it is a sip call, if it is a pstn call to a user they will arrive with the from attribute with out the correct value, if the customer has a rule where he analyzes the spf voice mails will have the action where the etr decides. <br/> | <br/> | 29/08/2019 workaround will be adding a exception in the etr if the message is a voice mail.

|**Issue title**|**Behavior / Symptom**|**Known workaround**|**Discovery date**|
|:-----|:-----|:-----|:-----|
|Teams voicemail emails will arrive with spf fail if it is a sip call, if it is a pstn call to a user they will arrive with the from attribute without the correct value, if the customer has a rule where he analyzes the spf voice mails will have the action where the etr decides. <br/> | <br/> | 29/08/2019 workaround will be adding a exception in the etr if the message is a voice mail.

|**Issue title**|**Behavior / Symptom**|**Known workaround**|**Discovery date**|
|:-----|:-----|:-----|:-----|
Expand All @@ -366,10 +343,6 @@ This article lists the known issues for Microsoft Teams, by feature area.
|:-----|:-----|:-----|:-----|
|Team names that contain special characters can create errors for meeting creation <br/> |User will receive **error has occurred** message in red when trying to create a meeting for a Team that has special characters in the name. <br/> |Rename or recreate team with a name that does not contain a "/". <br/> |7/13/17 <br/> |

|**Issue title**|**Behavior / Symptom**|**Known workaround**|**Discovery date**|
|:-----|:-----|:-----|:-----|
|A team name with an &amp; symbol in it breaks connector functionality <br/> |When a team name is created with the &amp; symbol, connectors within the Team/Group cannot be established. <br/> |Don't use special characters in team names. <br/> |6/21/17 <br/> |

|**Issue title**|**Behavior / Symptom**|**Known workaround**|**Discovery date**|
|:-----|:-----|:-----|:-----|
|Team member maximum of 5000 <br/> |Each Microsoft Team can have a maximum of 5000 members per team. <br/> |No workaround. <br/> |2/6/2019 <br/> |
Expand All @@ -386,10 +359,6 @@ This article lists the known issues for Microsoft Teams, by feature area.
|:-----|:-----|:-----|:-----|
|User not receiving welcome email when added administratively <br/> |When adding a member to a team using PowerShell or the Teams admin center, they are not receiving a welcome email from Microsoft Teams <br/> |Adding a member from the Teams UI directly will send an email. Currently, there is no workaround doing so administratively. <br/> |2/12/19 <br/> |

|**Issue title**|**Behavior / Symptom**|**Known workaround**|**Discovery date**|
|:-----|:-----|:-----|:-----|
|Unable to move, delete or rename files after editing <br/> |After a file is edited in Teams it cannot be moved or renamed or deleted immediately <br/> |This is currently a known issue and the workaround is to wait for some time before making administrative changes. <br/> |03/12/19 <br/> |

|**Issue title**|**Behavior / Symptom**|**Known workaround**|**Discovery date**|
|:-----|:-----|:-----|:-----|
|Interoperability issue between Symantec DLP and Teams <br/> |Symantec DLP Endpoint agents can interfere with Teams process, which can then lead to a launch or exit failure. <br/> |Exclude (whitelist) Teams.exe from the Symantec DLP's Endpoint agents as described in this <a href="https://support.symantec.com/us/en/article.TECH220322.html">Symantec support article</a>. <br/> |07/15/19 <br/> |
Expand Down