Important: The GCConnex decommission will not affect GCCollab or GCWiki. Thank you and happy collaborating!

Difference between revisions of "M365/test4"

From wiki
Jump to navigation Jump to search
Line 39: Line 39:
  
 
* Users can manually revise invitation messages as a stop-gap measure, but SSC is looking for a long-term solution from Microsoft that provides a full bilingual service.
 
* Users can manually revise invitation messages as a stop-gap measure, but SSC is looking for a long-term solution from Microsoft that provides a full bilingual service.
 
 
{| class="wikitable" border="1"
 
|- align="center"
 
| '''Milestones'''
 
| '''Responsibility'''
 
| '''Progress Update'''
 
|- 
 
| Testing Pilot: Establish a testing environment for each participating tenants (Tenant ID)
 
| Microsoft
 
| Complete
 
|- 
 
| Testing Pilot in progress: Participants are in the testing environment.
 
| SSC/Microsoft
 
| Complete
 
|- 
 
| Testing completed and the testing result given to Microsoft
 
| SSC
 
| Complete
 
|- 
 
| Completion of Microsoft Internal Release Update Process
 
| Microsoft
 
| Complete
 
|- 
 
| SSC Collaboration Solutions' approval of the update release
 
| SSC
 
| Complete
 
|-
 
| Microsoft to release an update (MS Roadmap Feature ID 81521)
 
| Microsoft
 
| Complete
 
|-
 
| SSC-DCC Playbook creating a Play for this issue
 
| SSC
 
| Complete
 
|-
 
| SSC Communication CIO Communique Approval process
 
| SSC
 
| Complete
 
|-
 
| Communication of the new update release
 
| SSC
 
| On Track
 
|}
 
 
  
 
=== Data Loss Prevention (DLP) Notifications ===
 
=== Data Loss Prevention (DLP) Notifications ===
Line 98: Line 53:
  
 
* Users may not be able to address data loss prevention (DLP) issues or understand why an action has been blocked. This will lead to Official Languages complaints and reduced ability of the GC to use DLP policies.
 
* Users may not be able to address data loss prevention (DLP) issues or understand why an action has been blocked. This will lead to Official Languages complaints and reduced ability of the GC to use DLP policies.
 
{| class="wikitable" border="1"
 
|- align="center"
 
| '''Milestones'''
 
| '''Responsibility'''
 
| '''Progress Update'''
 
|- 
 
| Confirm if MS-suggested workarounds are acceptable
 
| SSC
 
| Complete
 
|- 
 
| Communicated the desired MS solution to Microsoft
 
| SSC
 
| Complete
 
|- 
 
| Request for Microsoft to open a Support Case
 
| Microsoft
 
| Complete
 
|- 
 
| Microsoft will perform tests and analyses to determine if a Design Change is required
 
| Microsoft
 
| Complete
 
|- 
 
| Technical Lead working with SSC DCC Design Solution Team on the new design solution
 
| SSC
 
| TBD*
 
|- 
 
| Technical Lead working with SSC DCC Design Solution Team on testing the new design solution
 
| SSC
 
| TBD*
 
|- 
 
| Microsoft to release the update
 
| Microsoft
 
| TBD*
 
|}
 
 
'''''*TBD''''': ''The milestone will not start until previous milestones are started/completed.''
 
  
 
=== Group Access Review Notification ===
 
=== Group Access Review Notification ===
Line 157: Line 75:
 
* The Group Access Review Notification is available only in English regardless of the fact the user has the settings in French​.
 
* The Group Access Review Notification is available only in English regardless of the fact the user has the settings in French​.
  
 
{| class="wikitable" border="1"
 
|- align="center"
 
| '''Milestones'''
 
| '''Responsibility'''
 
| '''Progress Update'''
 
|- 
 
| DCC UX issued reported to Microsoft
 
| SSC
 
| Complete
 
|- 
 
| Microsoft is asking SSC to open a request with MS Support Engineering Group
 
| Microsoft
 
| Complete
 
|- 
 
| DCC Solution Design to open a request with MS Support Engineering Group
 
| SSC
 
| Complete
 
|- 
 
| Microsoft Product Group Project Management assigned the Feature owner
 
| Microsoft
 
| Complete
 
|- 
 
| Microsoft Feature owner working to fix issue
 
| Microsoft
 
| Complete
 
|-
 
| Private Preview Testing
 
| SSC
 
| On Track
 
|-
 
| Microsoft to release an update
 
| Microsoft
 
| TBD*
 
|}
 
 
'''''*TBD''''': ''The milestone will not start until previous milestones are started/completed.''
 
 
=== Canadian French Dictate ===
 
=== Canadian French Dictate ===
  
Line 214: Line 95:
  
 
* French users are unable to use '''Dictate''', unlike the English users.
 
* French users are unable to use '''Dictate''', unlike the English users.
 
{| class="wikitable" border="1"
 
|- align="center"
 
| '''Milestones'''
 
| '''Responsibility'''
 
| '''Progress Update'''
 
|- 
 
| Issue reported to both Microsoft Official Languages team and Microsoft Enterprise Disability Answer Desk (eDAD)
 
| Microsoft
 
| Complete
 
|- 
 
| Issue is being analyzed by both Microsoft Official Languages team and Microsoft Enterprise Disability Answer Desk (eDAD)
 
| Microsoft
 
| Complete
 
|- 
 
| DCC Solution Design to open a request with MS Support Engineering Group
 
| SSC
 
| Complete
 
|- 
 
| Microsoft Product Group Project Management assigned the Feature owner
 
| Microsoft
 
| Complete
 
|- 
 
| Microsoft Feature owner working to fix issue
 
| Microsoft
 
| Complete
 
|-
 
| Microsoft to release an update
 
| Microsoft
 
| On Track
 
|}
 
 
  
 
=== Microsoft Teams Rooms (MTR)===
 
=== Microsoft Teams Rooms (MTR)===
Line 260: Line 109:
 
* SSC Conference Services Team will create a testing environment at 99 Metcalfe.
 
* SSC Conference Services Team will create a testing environment at 99 Metcalfe.
 
* Conference Services, DCC UX, and Microsoft Official Languages, Microsoft’s Enterprise Disability Answer Desk, SSC CIO Collaborations Solutions, and AAACT are collaborating on a potential fix.
 
* Conference Services, DCC UX, and Microsoft Official Languages, Microsoft’s Enterprise Disability Answer Desk, SSC CIO Collaborations Solutions, and AAACT are collaborating on a potential fix.
 
{| class="wikitable" border="1"
 
|- align="center"
 
| '''Milestones'''
 
| '''Responsibility'''
 
| '''Progress Update'''
 
|- 
 
| Issue reported to Microsoft Official Languages team
 
| SSC
 
| Complete
 
|- 
 
| Microsoft Product Group Project Management assigned the Feature owner
 
| Microsoft
 
| Complete
 
|- 
 
| Issue is being analyzed by Microsoft Official Languages team
 
| Microsoft
 
| Complete
 
|-
 
| Microsoft Feature owner working to fix issue
 
| Microsoft
 
| Complete
 
|-
 
| Microsoft to release an update
 
| Microsoft
 
| On Track
 
|}
 
 
 
 
  
 
=== Microsoft Teams Bookings ===
 
=== Microsoft Teams Bookings ===
Line 303: Line 122:
 
* Microsoft requested that DCC-UX Team meet with them to demonstrate the issue live. A meeting is pending.
 
* Microsoft requested that DCC-UX Team meet with them to demonstrate the issue live. A meeting is pending.
 
* DCC-UX opened a ticket with Microsoft, and the issue was assigned to a Microsoft engineering team.
 
* DCC-UX opened a ticket with Microsoft, and the issue was assigned to a Microsoft engineering team.
 
 
{| class="wikitable" border="1"
 
|- align="center"
 
| '''Milestones'''
 
| '''Responsibility'''
 
| '''Progress Update'''
 
|- 
 
| Issue reported to Microsoft - Official Languages Team (Case Number: 2304130060001773)
 
| SSC
 
| Complete
 
|- 
 
| Microsoft Product Group Project Management assigned to Microsoft Engineering Team
 
| Microsoft
 
| Complete
 
|- 
 
| Issue being analyzed by a Microsoft team
 
| Microsoft
 
| On Track
 
|-
 
| Microsoft Feature owner working to fix issue
 
| Microsoft
 
| On Track
 
|-
 
| Microsoft to release an update
 
| Microsoft
 
| TBD*
 
|}
 
 
'''''*TBD''''': ''The milestone will not start until previous milestones are started/completed.''
 
 
  
 
=== Microsoft Yammer Missing the Bilingual E-mail Notification ===
 
=== Microsoft Yammer Missing the Bilingual E-mail Notification ===
Line 345: Line 133:
 
* DCC-UX Team opened a ticket with Microsoft, and the issue was assigned to a Microsoft engineering team.
 
* DCC-UX Team opened a ticket with Microsoft, and the issue was assigned to a Microsoft engineering team.
 
* Microsoft requires more information from the reporting GC partner.  
 
* Microsoft requires more information from the reporting GC partner.  
 
 
{| class="wikitable" border="1"
 
|- align="center"
 
| '''Milestones'''
 
| '''Responsibility'''
 
| '''Progress Update'''
 
|- 
 
| Issue reported to Microsoft
 
| SSC
 
| Complete
 
|- 
 
| Microsoft Product Group Project Management assigned to Microsoft Engineering Team
 
| Microsoft
 
| Complete
 
|- 
 
| Issue being analyzed by a Microsoft team
 
| Microsoft
 
| Complete
 
|-
 
| Microsoft working to fix issue
 
| Microsoft
 
| On Track
 
|-
 
| Microsoft to release an update
 
| Microsoft
 
| TBD*
 
|}
 
 
'''''*TBD''''': ''The milestone will not start until previous milestones are started/completed.''
 
 
  
 
== Archived Official Languages Issues==
 
== Archived Official Languages Issues==
Line 387: Line 144:
 
* The MS Product team confirmed that the request cannot be accepted. Microsoft is putting their effort into project.microsoft.com.
 
* The MS Product team confirmed that the request cannot be accepted. Microsoft is putting their effort into project.microsoft.com.
 
* Microsoft closed the ticket.
 
* Microsoft closed the ticket.
 
{| class="wikitable" border="1"
 
|- align="center"
 
| '''Milestones'''
 
| '''Responsibility'''
 
| '''Progress Update'''
 
|- 
 
| Issue reported to Microsoft - Official Languages Team Case Number: 2303240060001234
 
| SSC
 
| Complete
 
|- 
 
| Microsoft Product Group Project Management assigned to Microsoft Engineering Team
 
| Microsoft
 
| Complete
 
|- 
 
| Issue being analyzed by a Microsoft team
 
| Microsoft
 
| Complete
 
|-
 
| Ticket Closed
 
| Microsoft
 
| Complete
 
|}
 
 
 
  
 
=== Microsoft Visio not Available in Canadian French  (FR-CA) - Closed ===
 
=== Microsoft Visio not Available in Canadian French  (FR-CA) - Closed ===
Line 425: Line 157:
 
* Microsoft Product Groups team has rejected the request to create the Canadian French version on their product.
 
* Microsoft Product Groups team has rejected the request to create the Canadian French version on their product.
 
* Microsoft offered a workaround of an FR-FR option that is set when selecting French (Canada).
 
* Microsoft offered a workaround of an FR-FR option that is set when selecting French (Canada).
 
{| class="wikitable" border="1"
 
|- align="center"
 
| '''Milestones'''
 
| '''Responsibility'''
 
| '''Progress Update'''
 
|- 
 
| Issue reported to Microsoft - Official Languages Team Case Number: 2303240010001370
 
| SSC
 
| Complete
 
|- 
 
| Microsoft Product Group Project Management assigned to Microsoft Engineering Team
 
| Microsoft
 
| Complete
 
|- 
 
| Issue being analyzed by a Microsoft team
 
| Microsoft
 
| Complete
 
|-
 
| Ticket Closed
 
| Microsoft
 
| Complete
 
|}
 
 
  
 
=== System-generated E-mails - Closed ===
 
=== System-generated E-mails - Closed ===
Line 466: Line 174:
 
* The CIO Communique will include the System Generated Emails and the Audio-Conferencing Dial-in.  
 
* The CIO Communique will include the System Generated Emails and the Audio-Conferencing Dial-in.  
 
* The Play has been completed and added to Playbook: [https://www.gcpedia.gc.ca/wiki/M365-playbook/business-integration#System_Generated_Email_Policy_PIN System Generated Email].  
 
* The Play has been completed and added to Playbook: [https://www.gcpedia.gc.ca/wiki/M365-playbook/business-integration#System_Generated_Email_Policy_PIN System Generated Email].  
 
 
{| class="wikitable" border="1"
 
|- align="center"
 
| '''Milestones'''
 
| '''Responsibility'''
 
| '''Progress Update'''
 
|- 
 
| Phase 1 Communications: Play published in Playbook
 
| SSC
 
| Complete
 
|- 
 
| Revision of drafted Communications (Technical Briefs)
 
| SSC
 
| Complete
 
|- 
 
| CIO Communications: Draft, Proofreading, and Translation
 
| SSC
 
| Complete
 
|- 
 
| SSC Communication CIO Communique Approval process
 
| SSC
 
| Complete
 
|- 
 
| CIO Communications sent
 
| SSC
 
| Complete
 
|}
 
 
  
 
=== Teams Meeting French Canadian Captioning and Subtitles - Closed ===
 
=== Teams Meeting French Canadian Captioning and Subtitles - Closed ===

Revision as of 10:14, 27 January 2025

Click here to return to Accessible-M365

Purpose[edit | edit source]

  • To provide detailed bi-weekly status updates on Microsoft 365 (M365) Official Languages Issues, and on how they are addressed to meet the OL requirements by the GC.
  • To provide overall status updates on Microsoft 365 (M365) Official Languages Issues.

Context[edit | edit source]

The Government of Canada is committed to providing a workplace that respects both official languages at all times, and to maintaining a qualified and competent workforce that is capable of delivering services of the highest quality to its internal and external clients in the language of their choice.

The Official Languages Act dictates that English and French are the languages of work in federal institutions. By ensuring that M365 Products respect the Official Languages Act, the SSC Digital Communication and Collaborations (DCC) – User Experience (UX) is assisting the federal institutions:

  • to respect the language-of-work rights of employees, and
  • to create and maintain a workplace that is conducive to the use of English and French in bilingual regions, for example by holding bilingual meetings.

By ensuring that M365 Products align with the Official Languages Act, DCC UX team is contributing to the Government of Canada’s duty to accommodate and maintain an inclusive and linguistically barrier-free environment in the workplace. Therefore, tracking the M365 Official Languages Issues and resolving them is important as those issues can easily turn into high visibility cases.


Official Languages Issues Reports[edit | edit source]

Teams Meeting Invitations - Outlook Add-In[edit | edit source]

Description[edit | edit source]
  • Invitations sent to participants in Outlook by a meeting organizer are written in only one language, the organizer’s preferred language.
  • Adding a bilingual message was tested using existing Teams features as a potential stop gap; long term solution is to deploy a new Teams plug-in for Outlook that supports bilingual meeting invitations. Using a bilingual logo was tested; however, the solution is not viable as it would break current security controls (i.e., allowing automatic download of images from a URL). Microsoft created a formal Design Change Request (DCR); SSC awaits the new functionality.
Status and Updates[edit | edit source]
  • Microsoft requested a Business Impact Statement from SSC for the requested corrections. Microsoft will decide which requests of the French portion of the Teams Meeting Invitations they will work on.
  • Microsoft will do additional corrections to the French  portion of the bilingual invitation.
  • SSC Official Languages team has reviewed and approved the requested French corrections to ensure that  they align with the Official Languages Act.
  • DCC UX instructed SSC CIO Communication to remove Teams Meeting Invitation-Outlook Add-in from the CIO Communique. A separate communique will be done for this issue.
  • The language setting chosen in MS teams will dictate what language the user will see.
  • Teams admins will be responsible for configuring some of the hyperlinks contained in the Teams invitations. Related instructions have been added to the Play.
  • Link to Play: Official Languages Outlook meeting invitations.
Risk[edit | edit source]
  • Users can manually revise invitation messages as a stop-gap measure, but SSC is looking for a long-term solution from Microsoft that provides a full bilingual service.

Data Loss Prevention (DLP) Notifications[edit | edit source]

Description[edit | edit source]
  • Partners can define M365 policies that prevent people from sharing sensitive information when using M365 products such as Teams, Email, Excel, Word, PowerPoint, OneDrive, and SharePoint.
  • Currently, notifications to users about data loss prevention are unilingual.
Status and Updates[edit | edit source]
  • DCC-UX followed up with Microsoft for an update and is still waiting.
  • Microsoft confirmed that the issue is classified as a Design Change Request. The task was assigned to a Technical Lead (Case# 31444691). The estimated completion target date is Q1 or Q2 2023 (2023-09-30). The work will start in Q1 (April 2023).
Risk[edit | edit source]
  • Users may not be able to address data loss prevention (DLP) issues or understand why an action has been blocked. This will lead to Official Languages complaints and reduced ability of the GC to use DLP policies.

Group Access Review Notification[edit | edit source]

Description[edit | edit source]
  • When renewing guest users, it is not possible to change the notification text to French, nor change the content to be bilingual. The Access Review Notification email is sent to the main tenant’s language choice only, and not to the user’s choice of language.
  • The Access Review Notification email contains two links: Perform an Access Review and Azure Active Directory Access Review. When clicking on either link, it will open in the Edge browser in the language choice that was set by the user. The message is not bilingual.
Status and Updates[edit | edit source]
  • Microsoft has archived the service request awaiting the testing in private preview to be complete.
  • SSC contacted GC partners to provide volunteers with admin access at the M365 Tenant level to help perform the testing with the Group Access Review Notification feature with Microsoft.
  • Microsoft reported the feature is currently in development, but no estimated release date given yet.
  • Microsoft asked if DCC-UX is willing to be added into the private preview to test the feature once available (Case Number 2304120030002838)
  • Microsoft has assigned a support engineer to follow up on the issue.
  • DCC-UX is drafting a list of users who could be interested in accessing the private preview.
  • Microsoft has opened the ticket.
  • The issue was reported to Microsoft on 2022-04-11.
Risk[edit | edit source]
  • The Group Access Review Notification is available only in English regardless of the fact the user has the settings in French​.

Canadian French Dictate[edit | edit source]

Description[edit | edit source]
  • Canadian French Dictate is a voice-to-text author that is used to create documents.
  • In this case, it is used to create a Word document via the web-version of Word.
  • The French (Canada) Dictate feature does not work on the Web version of MS Word. Despite having all settings activated, the feature still does not work. It appears that this is a wide-scale SSC issue. This issue is concerning as it affects both Accessibility and Official Languages obligations.
Status and Updates[edit | edit source]
  • French Dictate solution is in private preview.
  • DCC-UX is waiting for the release date of the update by Microsoft.
  • DCC-UX requested DCC Playbook to create the Play for this feature.
  • SSC-AAACT confirmed the issue is resolved.
  • Microsoft updated DCC-UX with steps to verify the potential resolution for this issue. These instructions were shared with the GC partner who reported the issue. DCC-UX is awaiting their testing results to confirm the resolution and closing of this issue.
  • SSC-UX is still awaiting a similar confirmation from a GC Partner.
  • Microsoft Product Group’s analysis is underway.
  • Since this issue affects both official languages and accessibility, the two Microsoft teams of Official Languages and eDAD are working in coordination on the issue. 
Risk[edit | edit source]
  • French users are unable to use Dictate, unlike the English users.

Microsoft Teams Rooms (MTR)[edit | edit source]

Description[edit | edit source]
  • Microsoft Teams Rooms (MTR) interface does not allow users to choose the language of their choice. Users must log out for them to be able choose their language of choice.​
Status and Updates[edit | edit source]
  • SSC Conferencing Services Team is currently working with the DCC Playbook Team to create the MTR Play and any additional Plays that may be required for the launch of the MTR service.
  • Microsoft has resolved the issue and there is a bilingual interface available in public preview. The Update will be released by the end of July 2023.
  • AAACT is to advise SSC Conference Services when they will begin testing on site.
  • Microsoft assigned the issue to an engineering team to work on the ability to change the languages on Microsoft Teams Rooms (MTR)/Surface Hub. The task is scheduled for the first half of 2023. Dates are subject to change.
  • SSC Conference Services Team will create a testing environment at 99 Metcalfe.
  • Conference Services, DCC UX, and Microsoft Official Languages, Microsoft’s Enterprise Disability Answer Desk, SSC CIO Collaborations Solutions, and AAACT are collaborating on a potential fix.

Microsoft Teams Bookings[edit | edit source]

Description[edit | edit source]
  • In the Teams Bookings App, a calendar page can only be made available in either English or French, not giving the user the option to choose both. 
  • A minimum of two languages should be set on the Bookings page, allowing the recipient to toggle to the Official language of their choice.
  • The current workaround is to create separate calendars (one in French, one in English) and to send two separate links to the recipient.
  • The names of the Bookings titles, descriptions, and service titles can be changed to reflect both the English and the French languages. However, toggling between English and French is not possible for the hard-coded titles, such as SELECT A SERVICE, SELECT STAFF, TIME, ADD YOUR DETAILS.
Status and Updates[edit | edit source]
  • Microsoft requested that DCC-UX Team meet with them to demonstrate the issue live. A meeting is pending.
  • DCC-UX opened a ticket with Microsoft, and the issue was assigned to a Microsoft engineering team.

Microsoft Yammer Missing the Bilingual E-mail Notification[edit | edit source]

Description[edit | edit source]
  • Yammer is fully bilingual, except for the notification sent via email or Teams.
Status and Updates[edit | edit source]
  • DCC-UX Team provided Microsoft with further details as per their request.
  • DCC-UX Team provided more details on the issue as requested by Microsoft.
  • DCC-UX Team opened a ticket with Microsoft, and the issue was assigned to a Microsoft engineering team.
  • Microsoft requires more information from the reporting GC partner.

Archived Official Languages Issues[edit | edit source]

MS Project not Available in Canadian French (FR-CA) - Closed[edit | edit source]

Description[edit | edit source]
  •  MS Project is not available in Canadian French (FR-CA).
Status and Updates[edit | edit source]
  • Ticket is closed.
  • Microsoft confirmed that MS Project is only available in France French (FR-FR).
  • DCC-UX opened a ticket with Microsoft requesting that a Canadian French version be created.
  • The MS Product team confirmed that the request cannot be accepted. Microsoft is putting their effort into project.microsoft.com.
  • Microsoft closed the ticket.

Microsoft Visio not Available in Canadian French (FR-CA) - Closed[edit | edit source]

Description[edit | edit source]
  •   MS Visio is not available in Canadian French (FR-CA).
Status and Updates[edit | edit source]
  • Ticket is closed.
  • Microsoft confirmed that no further investment will be done on Visio. They are fully focused on project on the Web (project.Microsoft.com)
  • Microsoft confirmed that MS Visio is only available in France French (FR-FR).
  • DCC-UX opened a ticket with Microsoft requesting that a Canadian French version be created.
  • Microsoft Product Groups team has rejected the request to create the Canadian French version on their product.
  • Microsoft offered a workaround of an FR-FR option that is set when selecting French (Canada).

System-generated E-mails - Closed[edit | edit source]

Description[edit | edit source]
  • Portal language and system generated emails are based on the users’ preferred language as set in Active Directory (AD).
  • Departments must populate this field for all their users in order to see this change take effect.
  • SSC is offering guidance and assistance to any department requiring it; some partners, such as ESDC, who use the preferred language field for other purposes, will need additional support from Directory Services.
  • Resolved by setting and synchronizing the preferred Language AD attribute. Working with TBS to add to guardrails.  CIO Communications are being developed.
Status and Updates[edit | edit source]
  • DCC UX instructed SSC CIO Communication to remove Teams Meeting Invitation-Outlook Add-in from the CIO Communique.
  • The CIO Communique will include the System Generated Emails and the Audio-Conferencing Dial-in.
  • The Play has been completed and added to Playbook: System Generated Email.

Teams Meeting French Canadian Captioning and Subtitles - Closed[edit | edit source]

Description[edit | edit source]
  • Coming soon


Status and Updates[edit | edit source]
  • Live Captioning in Teams meetings is available in preview mode, English-only. This feature can be disabled or used in limited state by departments until it is production-ready.
  • Captioning does not support switching between spoken languages; DCC is sharing requirements with Microsoft product engineers.
  • SSC has rolled out this feature launched by MS in August 2021.
Milestone Responsibility Progress Update
Teams Meeting French (Canada) Captioning deployment/availability (MS Roadmap Feature ID 83615) Microsoft Complete
Teams Live Events French (Canada) subtitles deployment/availability (MS Roadmap Feature ID 70593) Microsoft Complete


Multiple Audio Streams for Translation - Closed[edit | edit source]

Description[edit | edit source]
  • Multiple Audio Streams is a built-in feature in Teams meetings that would allow human interpreters join a meeting to translate into a specific language and use an audio channel, and allow attendees to subscribe to a specific audio channel for listening and speaking in their language of choice.


Status and Updates[edit | edit source]
  • The feature is now available to the general public and a CIO Communique will be sent
  • Link: Language Interpretation in a Teams Meeting
  • No configuration required to be done by M365 General Admins
  • No Play is required in Playbook


Milestones Responsibility Progress Update
Issue reported to Microsoft SSC Complete
Microsoft Product Group Project Management assigned the Feature owner Microsoft Complete
Microsoft Feature owner working to fix issue Microsoft Complete
Feature(fix) available in Public Preview Microsoft Complete
Microsoft to release an update (DCR890358) Microsoft Complete

Audio-Conferencing Dial-in Message - Closed[edit | edit source]

Description[edit | edit source]
  • Users connecting to Teams meetings hear an English message, and after a long pause, have the option to choose their preferred language, and then can receive all prompts in French.
  • Dial-in service is being changed to give a language selection prompt first, but departments will need to ensure they are using a dedicated phone bridge, not a shared phone number. Two numbers are required, one for English and another for French.
Status and Updates[edit | edit source]
  • DCC-UX instructed SSC CIO Communication to remove Teams Meeting Invitation-Outlook Add-in from the CIO Communique.
  • The CIO Communique will include the System Generated Emails and the Audio-Conferencing Dial-in.
  • Release update is complete and CIO communication now ready to be sent.
  • Link to Play: Audio-Conferencing Dial-in Message  
Milestones Responsibility Progress Update
Teams Audio Dial-in Bilingual Options (DCR1564271) Microsoft Complete
Compiling a List of Tenant IDs and Dedicated Conference Bridge Numbers SSC Complete
Verification and Confirmation that Microsoft updates will not affect Global Settings SSC Complete
Provide the compiled list to Microsoft SSC Complete
Completion of Microsoft Internal Release Update Process Microsoft Complete
Microsoft to deploy the Audio Dial-in update to the compiled list Microsoft Complete
SSC-DCC Playbook creating a Play for this issue SSC Complete
SSC Communication CIO Communique Approval process SSC Complete
Communication of the new update release SSC Complete


MS Teams Auto-correct and Auto-detect - Closed[edit | edit source]

Description[edit | edit source]
  • Coming soon
Status and Updates[edit | edit source]
  • Spellchecking across multiple languages was originally rolled out to Teams Desktop App on Windows, this was later rolled back so the feature can be improved upon. The feature is still available on some tenants but not always consistently functioning.
  • Fix is saturating successfully throughout the impacted environments, MS is continuing to monitor progression. Deployment remains on track.
  • MS continues to verify new functionality.
  • New MS ticket opened to verify fix works as designed. MS continues to verify new functionality.
Milestone Responsibility Progress Update
A recent deployment to optimize the multi-language spellcheck functionality with Microsoft Teams inadvertently

introduced a network configuration issue that is resulting in impact. MSID: TM259318

Microsoft Complete


Contact Us[edit | edit source]

DCC.Accessibility (SSC),dcc.accessibility-accessibilite.cnn@ssc-spc.gc.ca


Click here to return to Accessible-M365