New Policy Enforces Three-Month Limit for Teams Desktop Client
On October 15, Microsoft published Office 365 Notification MC193099 to reveal that Teams is “governed by the Modern Lifecycle Policy” and that this means that users are expected to keep the Teams desktop client updated. The FAQ for Microsoft’s Modern Lifecycle Policy says that “Products… are supported as long as customers stay current…” and that to stay current “a customer must accept all servicing updates and apply them within a specific timeframe,”
Microsoft doesn’t give precise details as to when they will enforce the Modern Lifecycle Policy for Teams. They do say that the update will roll out in three phases and that ” If users in your organization will encounter these in-app notifications, we will be notifying you via Message Center. ” Quite what that means in practice remains to be seen.
Teams Updates Available Every Two Weeks
Teams is in a state of fast evolution and Microsoft usually releases new builds every two weeks. To stay current, you should apply the updates as they are released. Apart from updating to apply bug fixes, you’ll also gain access to new features. Teams makes it easy to apply updates as the client automatically checks for new software every few hours and will download and apply an update in the background once the system is idle. You might have to refresh (reload) the client to complete an update cycle, but the process is pretty easy and doesn’t normally cause problems.
To find out what version of Teams is running on a workstation, click the user avatar (photo) in the top bar and choose About and then Version from the menu (Figure 1).
Figure 1: How to check for Teams software updates
The client lists the current version number and the date the last software update was applied to the client in a banner at the top of the screen (Figure 2)
Figure 2: Teams tells you what software version the desktop client runs
Factors Preventing Updates
As the notification points out, it’s possible that some factors get in the way of the Teams auto-update routine. The most interesting scenario is when people use Teams exclusively for meetings and calls because the auto-update routine doesn’t run when these events happen (to ensure that background processing doesn’t interfere with smooth video and audio performance).
Three Months is the Maximum Age for the Teams Desktop Client
MC193099 clearly lays out that Microsoft considers three months to be the absolute maximum for a Teams desktop client to lag behind the current release. In fact, once a client is more than a month old, Teams begins to display a polite nagging banner to cheerfully inform the user that “Looks like you’re on an old version of Teams.” A link to download the latest update is included in the banner.
Things get more serious as the three-month deadline approaches. The banner begins a countdown to note how many days the user has to update to continue using the app. If the threshold is reached, Teams blocks access and flatly tells the user that they either have to update now or continue to use the browser client. Or, if a friendly IT administrator is available, maybe they can solve the problem by applying the update.
Microsoft gives a 28-day grace period to fresh installations of the desktop client that use old software, but the grace period is solely to allow Teams to auto-update in the background. Once the 28-day grace period elapses, Teams imposes the block.
Need help to understand how Teams works? Look no further than the Office 365 for IT Pros eBook. We update the eBook monthly to make sure that we include important information like the material discussed in this post.
Maybe they should have considered all this when they designed the installer and update mechanisms for teams. Per user installs, to appdata, to try and circumvent IT policies on software installation. Leading to more vulnerable PCs trying to relax security so it will update and install for the end user. Not to mention the issues that causes for VDI/RDS deployments. It should be installed per machine and updated through windows updates like defender and the rest of office apps. Ridiculous.
This update process is broken. I have clients with the “latest” version showing up but still getting this message.
Likewise, I have 5 different people on my team, each of us has checked for updates, the Teams client says we are up-to-date, yet we have different version numbers.
why this isn’t handled like all our other Microsoft updates is mind boggling.
{"id":null,"mode":"button","open_style":"in_modal","currency_code":"EUR","currency_symbol":"\u20ac","currency_type":"decimal","blank_flag_url":"https:\/\/office365itpros.com\/wp-content\/plugins\/tip-jar-wp\/\/assets\/images\/flags\/blank.gif","flag_sprite_url":"https:\/\/office365itpros.com\/wp-content\/plugins\/tip-jar-wp\/\/assets\/images\/flags\/flags.png","default_amount":100,"top_media_type":"featured_image","featured_image_url":"https:\/\/office365itpros.com\/wp-content\/uploads\/2022\/11\/cover-141x200.jpg","featured_embed":"","header_media":null,"file_download_attachment_data":null,"recurring_options_enabled":true,"recurring_options":{"never":{"selected":true,"after_output":"One time only"},"weekly":{"selected":false,"after_output":"Every week"},"monthly":{"selected":false,"after_output":"Every month"},"yearly":{"selected":false,"after_output":"Every year"}},"strings":{"current_user_email":"","current_user_name":"","link_text":"Virtual Tip Jar","complete_payment_button_error_text":"Check info and try again","payment_verb":"Pay","payment_request_label":"Office 365 for IT Pros","form_has_an_error":"Please check and fix the errors above","general_server_error":"Something isn't working right at the moment. Please try again.","form_title":"Office 365 for IT Pros","form_subtitle":null,"currency_search_text":"Country or Currency here","other_payment_option":"Other payment option","manage_payments_button_text":"Manage your payments","thank_you_message":"Thank you for supporting the work of Office 365 for IT Pros!","payment_confirmation_title":"Office 365 for IT Pros","receipt_title":"Your Receipt","print_receipt":"Print Receipt","email_receipt":"Email Receipt","email_receipt_sending":"Sending receipt...","email_receipt_success":"Email receipt successfully sent","email_receipt_failed":"Email receipt failed to send. Please try again.","receipt_payee":"Paid to","receipt_statement_descriptor":"This will show up on your statement as","receipt_date":"Date","receipt_transaction_id":"Transaction ID","receipt_transaction_amount":"Amount","refund_payer":"Refund from","login":"Log in to manage your payments","manage_payments":"Manage Payments","transactions_title":"Your Transactions","transaction_title":"Transaction Receipt","transaction_period":"Plan Period","arrangements_title":"Your Plans","arrangement_title":"Manage Plan","arrangement_details":"Plan Details","arrangement_id_title":"Plan ID","arrangement_payment_method_title":"Payment Method","arrangement_amount_title":"Plan Amount","arrangement_renewal_title":"Next renewal date","arrangement_action_cancel":"Cancel Plan","arrangement_action_cant_cancel":"Cancelling is currently not available.","arrangement_action_cancel_double":"Are you sure you'd like to cancel?","arrangement_cancelling":"Cancelling Plan...","arrangement_cancelled":"Plan Cancelled","arrangement_failed_to_cancel":"Failed to cancel plan","back_to_plans":"\u2190 Back to Plans","update_payment_method_verb":"Update","sca_auth_description":"Your have a pending renewal payment which requires authorization.","sca_auth_verb":"Authorize renewal payment","sca_authing_verb":"Authorizing payment","sca_authed_verb":"Payment successfully authorized!","sca_auth_failed":"Unable to authorize! Please try again.","login_button_text":"Log in","login_form_has_an_error":"Please check and fix the errors above","uppercase_search":"Search","lowercase_search":"search","uppercase_page":"Page","lowercase_page":"page","uppercase_items":"Items","lowercase_items":"items","uppercase_per":"Per","lowercase_per":"per","uppercase_of":"Of","lowercase_of":"of","back":"Back to plans","zip_code_placeholder":"Zip\/Postal Code","download_file_button_text":"Download File","input_field_instructions":{"tip_amount":{"placeholder_text":"How much would you like to tip?","initial":{"instruction_type":"normal","instruction_message":"How much would you like to tip? Choose any currency."},"empty":{"instruction_type":"error","instruction_message":"How much would you like to tip? Choose any currency."},"invalid_curency":{"instruction_type":"error","instruction_message":"Please choose a valid currency."}},"recurring":{"placeholder_text":"Recurring","initial":{"instruction_type":"normal","instruction_message":"How often would you like to give this?"},"success":{"instruction_type":"success","instruction_message":"How often would you like to give this?"},"empty":{"instruction_type":"error","instruction_message":"How often would you like to give this?"}},"name":{"placeholder_text":"Name on Credit Card","initial":{"instruction_type":"normal","instruction_message":"Enter the name on your card."},"success":{"instruction_type":"success","instruction_message":"Enter the name on your card."},"empty":{"instruction_type":"error","instruction_message":"Please enter the name on your card."}},"privacy_policy":{"terms_title":"Terms and conditions","terms_body":null,"terms_show_text":"View Terms","terms_hide_text":"Hide Terms","initial":{"instruction_type":"normal","instruction_message":"I agree to the terms."},"unchecked":{"instruction_type":"error","instruction_message":"Please agree to the terms."},"checked":{"instruction_type":"success","instruction_message":"I agree to the terms."}},"email":{"placeholder_text":"Your email address","initial":{"instruction_type":"normal","instruction_message":"Enter your email address"},"success":{"instruction_type":"success","instruction_message":"Enter your email address"},"blank":{"instruction_type":"error","instruction_message":"Enter your email address"},"not_an_email_address":{"instruction_type":"error","instruction_message":"Make sure you have entered a valid email address"}},"note_with_tip":{"placeholder_text":"Your note here...","initial":{"instruction_type":"normal","instruction_message":"Attach a note to your tip (optional)"},"empty":{"instruction_type":"normal","instruction_message":"Attach a note to your tip (optional)"},"not_empty_initial":{"instruction_type":"normal","instruction_message":"Attach a note to your tip (optional)"},"saving":{"instruction_type":"normal","instruction_message":"Saving note..."},"success":{"instruction_type":"success","instruction_message":"Note successfully saved!"},"error":{"instruction_type":"error","instruction_message":"Unable to save note note at this time. Please try again."}},"email_for_login_code":{"placeholder_text":"Your email address","initial":{"instruction_type":"normal","instruction_message":"Enter your email to log in."},"success":{"instruction_type":"success","instruction_message":"Enter your email to log in."},"blank":{"instruction_type":"error","instruction_message":"Enter your email to log in."},"empty":{"instruction_type":"error","instruction_message":"Enter your email to log in."}},"login_code":{"initial":{"instruction_type":"normal","instruction_message":"Check your email and enter the login code."},"success":{"instruction_type":"success","instruction_message":"Check your email and enter the login code."},"blank":{"instruction_type":"error","instruction_message":"Check your email and enter the login code."},"empty":{"instruction_type":"error","instruction_message":"Check your email and enter the login code."}},"stripe_all_in_one":{"initial":{"instruction_type":"normal","instruction_message":"Enter your credit card details here."},"empty":{"instruction_type":"error","instruction_message":"Enter your credit card details here."},"success":{"instruction_type":"normal","instruction_message":"Enter your credit card details here."},"invalid_number":{"instruction_type":"error","instruction_message":"The card number is not a valid credit card number."},"invalid_expiry_month":{"instruction_type":"error","instruction_message":"The card's expiration month is invalid."},"invalid_expiry_year":{"instruction_type":"error","instruction_message":"The card's expiration year is invalid."},"invalid_cvc":{"instruction_type":"error","instruction_message":"The card's security code is invalid."},"incorrect_number":{"instruction_type":"error","instruction_message":"The card number is incorrect."},"incomplete_number":{"instruction_type":"error","instruction_message":"The card number is incomplete."},"incomplete_cvc":{"instruction_type":"error","instruction_message":"The card's security code is incomplete."},"incomplete_expiry":{"instruction_type":"error","instruction_message":"The card's expiration date is incomplete."},"incomplete_zip":{"instruction_type":"error","instruction_message":"The card's zip code is incomplete."},"expired_card":{"instruction_type":"error","instruction_message":"The card has expired."},"incorrect_cvc":{"instruction_type":"error","instruction_message":"The card's security code is incorrect."},"incorrect_zip":{"instruction_type":"error","instruction_message":"The card's zip code failed validation."},"invalid_expiry_year_past":{"instruction_type":"error","instruction_message":"The card's expiration year is in the past"},"card_declined":{"instruction_type":"error","instruction_message":"The card was declined."},"missing":{"instruction_type":"error","instruction_message":"There is no card on a customer that is being charged."},"processing_error":{"instruction_type":"error","instruction_message":"An error occurred while processing the card."},"invalid_request_error":{"instruction_type":"error","instruction_message":"Unable to process this payment, please try again or use alternative method."},"invalid_sofort_country":{"instruction_type":"error","instruction_message":"The billing country is not accepted by SOFORT. Please try another country."}}}},"fetched_oembed_html":false}
Maybe they should have considered all this when they designed the installer and update mechanisms for teams. Per user installs, to appdata, to try and circumvent IT policies on software installation. Leading to more vulnerable PCs trying to relax security so it will update and install for the end user. Not to mention the issues that causes for VDI/RDS deployments. It should be installed per machine and updated through windows updates like defender and the rest of office apps. Ridiculous.
This update process is broken. I have clients with the “latest” version showing up but still getting this message.
Likewise, I have 5 different people on my team, each of us has checked for updates, the Teams client says we are up-to-date, yet we have different version numbers.
why this isn’t handled like all our other Microsoft updates is mind boggling.