September 2026 Update: Includes Dec 30, 2026 as the End of Support date for Impact by Instructure, Respondus Lockdown Browser. Amaplex, Biosig, Honorlock, Smowl. Additional extension for EAC until June 30, 2027.
August 2026 Update: Building Block integrations no longer supported by Third Parties as of August 30 2026: ReadSpeaker, Examity, Watermark – Evaluation Kit, Explorance Blue Course Evaluation, Dublabs, Sumadi.
September 2024 Update: Includes extension for Panopto, Echo 360 until December 30, 2024.
August 2024 Update: Includes extension for Kaltura until September 30, 2024 and adds further details on difference between End of Support date and Deactivation date.
June 2024 update: Includes extension for Panopto until September 30, 2024, Ellucian ILP REST API Integration details Ellucian community post link , steps for migration link, Cengage migration tool to LTI1.3 released link.
April 2024 Update: Includes additional partner integrations to the exception list Biosig, Examity, Honorlock, SMOWL, Sumadi, Dublabs, Explorance, Watermark. Additional extension for Echo360, Helix Media- Medial and Cengage Mindlinks. Update on migration tools delivery status, and inclusion of a new category for Building Block Support Status for JSHacks.
Cloud computing’s adoption in education has broadened the possibilities as SaaS models open a gateway for innovation, including next generation integration capabilities. To continue supporting our clients on their path to SaaS deployments, our goal is to ensure that our integration framework is SaaS aligned. With that in mind, as of January 1, 2024, Blackboard will wind down support for third-party Building Blocks (B2s) in Blackboard Learn and move to integrations based on REST APIs, 1EdTech LTI standards and Partner Cloud.
Important dates*:
December 31, 2022: Since this date, Blackboard reserves the right to restrict specific Java API (Building Block) access to Ultra courses based on required development for Ultra Course View.
July 6, 2022:
We announced additional details regarding authentication support and related best ractices here .
After Dec 31, 2023: ONLY bundled Building Block integrations or those with an approved exception or extension will be allowed on Learn instances.
Starting January 2024, only third-party Building Blocks with exceptions or receiving Extended Building Block Support can be installed or updated. Other third-party Building Blocks will be rejected.
After June 30, 2024: ONLY bundled Building Block integrations or those with an approved exception will be allowed on Learn instances.
Four (4) months after the Building Block is set to inactive, no longer allowed, we’ll remove them from client environments. After June 30, 2024: Any non-bundled Building Blocks or those without an approved exception will be set inactive from Learn SaaS instances. Grades associated with Building Blocks can be accessed in gradebooks, but content or links associated with Building Blocks can no longer be accessed. See details about data retrieval in this blog post. For self-hosted and Managed Hosting clients, non-bundled third-party Building Blocks or those without an approved exception or extension are also no longer supported.
Bundled Building Blocks that are the core part of the Blackboard Learn application continue to be supported. Only third-party Building Blocks added and managed by clients that haven’t received an exception are considered unsupported. See additional details below for identifying bundled Building Blocks.
For more details regarding the B2 Support path, please see also the Community Blog and our FAQ .
* IMPORTANT: Dates presented “Support Status” correspond to End Support (EOS) dates for the third party integrations, date after which support is expected to stop for the affected third party integrations. Following EOS Blackboard will perform building block deactivation activities, that are planned to be performed on the Learn release after the EOS deadline.
While the deactivation date is the day that we will turn off a Building Block automatically, we strongly recommend institutions set the affected Building Blocks to inactive prior to that. This allows institutions to manage the change in a way best suited to users. This includes managing timelines, communications, and the availability of support staff.