Microsoft 365 (and Office 365) subscribers get more frequent software updates than those who have purchased Office without a subscription, which means subscribers have access to the latest features, security patches, and bug fixes. But it can be hard to keep track of the changes in each update and know when theyβre available. Weβre doing this for you, so you donβt have to.
Following are summaries of the updates to Microsoft 365/Office 365 for Windows over the past year, with the latest releases shown first. Weβll add info about new updates as theyβre rolled out.
Note: This story covers updates released to the Current Channel for Microsoft 365/Office 365 subscriptions. If youβre a member of Microsoftβs Office Insider preview program or want to get a sneak peek at upcoming features, see the Microsoft 365 Insider blog.
Version 2605 (Build 20026.20168)
Release date: June 9, 2026
This build offers βvarious fixes to functionality and performance,β according to Microsoft.
This build fixes several bugs, including one in which Excel or PowerPoint closed unexpectedly in rare cases while the user was actively co-authoring, particularly when opening a documentΒ for the first time.
What IT needs to know: Because this is a security update, it should be applied relatively soon. Over the next few weeks, check for reports about problematic issues, and if all seems well, apply the update.
In this build, Copilot can now edit your PowerPoint documents. Copilot can start a new presentation or build on an existing one, generate slides, update content, improve layouts, and polish design, while preserving formatting, structure, and branding.Β
What IT needs to know: Because this is a security update, it should be applied relatively soon. Over the next few weeks, check for reports about problematic issues, and if all seems well, apply the update.
This build fixes several bugs, including one in Outlook in which users could not close the Copilot chat pane using a keyboard. Users can now close the pane by navigating to the Close button using a keyboard or by using the assigned keyboard shortcut.
This build fixes an Outlook bug in which updating a single instance of a recurring meeting in a Microsoft 365 group calendar updated the entire series.
This build introduces agent mode in Word, which adds a conversational chat experience that helps create, edit, and refine document content as you work. In addition, the build fixes a bug thatΒ impacted the rendering of extended characters in calendar items, causing certain characters to appear as question marks.
What IT needs to know: Because this is a security update, it should be applied relatively soon. Over the next few weeks, check for reports about problematic issues, and if all seems well, apply the update.
What IT needs to know: Because this is a security update, it should be applied relatively soon. Over the next few weeks, check for reports about problematic issues, and if all seems well, apply the update.
In this build, OneNote applies your chosen proofing language more consistently, so you donβt have to reset it for every paragraph when writing in multiple languages. In addition, the build fixes several bugs, including one that caused Office applications to become unresponsive when profile card-related activities were performed.
This build fixes a number of bugs, including one that caused Excel, PowerPoint, and Word to become unresponsive when profile card-related activities were performed.
What IT needs to know: Because this is a security update, it should be applied relatively soon. Over the next few weeks, check for reports about problematic issues, and if all seems well, apply the update.
This Patch Tuesday build offers, in Microsoftβs words, βVarious fixes to functionality and performance.β The build also has a variety of security updates (see details).
What IT needs to know: Because this is a security update, it should be applied relatively soon. Over the next few weeks, check for reports about problematic issues, and if all seems well, apply the update.
This Patch Tuesday build fixes a bug in Outlook that caused some recipients to be unable to access OneDrive links shared with them via email. The build also has a variety of security updates (see details).
What IT needs to know: Because this is a security update, it should be applied relatively soon. Over the next few weeks, check for reports about problematic issues, and if all seems well, apply the update.
This build has a variety of security updates (see details), along with various fixes to functionality and performance.
What IT needs to know: Because this is a security update, it should be applied relatively soon. Over the next few weeks, check for reports about problematic issues, and if all seems well, apply the update.
This build fixes two bugs, one in Excel in which ribbon controls were not rendered when rejoining Office sessions in a virtual machine, Azure Virtual Desktop, or remote desktop environment, and another that caused Outlook to terminate unexpectedly when starting.
This build has multiple security updates (see details), along with various fixes to functionality and performance.
What IT needs to know: Because this is a security update, it should be applied relatively soon. Over the next few weeks, check for reports about problematic issues, and if all seems well, apply the update.
This build fixes a bug that caused Outlook to terminate unexpectedly when sending a meeting invite with an encryption label. It also adds support for pixelated rendering of embedded images in SVG assets for the entire Office suite.
This build fixes a bug which required users to restart Outlook to open a .msg file after initially accessing it once. The build also includes a variety of security updates (see details).
What IT needs to know: Because this is a security update, it should be applied relatively soon. Over the next few weeks, check for reports about problematic issues, and if all seems well, apply the update.
This build fixes a wide variety of bugs, including in which Outlook closed unexpectedly shortly after launch, and another in Word in which the word count sometimes displayed incorrectly.
This build fixes two bugs, one that caused the Copilot Command Center to continue to be visible after disabling the Copilot user interface, and another in which when creating handouts in PowerPoint, certain characters (full-width numbers) couldnβt be properly transferred to the handout.
This build fixes two bugs, one that caused Visio 32-bit to close unexpectedly when using the Drawing control, particularly in setups involving COM components or .NET integrations, and another in Word in which copying and pasting content between documents sometimes changed the applied style unexpectedly.
This Patch Tuesday build fixes several bugs in Outlook, PowerPoint, Word, and the whole Office suite, including one that caused the Copilot icon to unexpectedly display in Outlook when Copilot had been disabled by the admin in government cloud.
The release also includes a variety of security updates (see details).
What IT needs to know: Because this is a security update, it should be applied relatively soon. Over the next few weeks, check for reports about problematic issues, and if all seems well, apply the update.
This build introduces several new features, including one in Excel in which the PivotTables dialog box interface has been replaced by a redesigned panel, making it easier to view all of your options and simpler to change your data selection before inserting a recommended PivotTable.
This build fixes a bug that caused the βTry the new Outlookβ toggle to be enabled when working in Classic Outlook side by side with the new Outlook.
This build fixes several bugs, including one for the entire Office suite in which a Save As attempt on an existing file didnβt complete successfully, and subsequent attempts continued to encounter issues when trying to save to a file that no longer existed.
This Patch Tuesday release also includes a variety of security updates: see details.
What IT needs to know: Because this is a security update, it should be applied relatively soon. Over the next few weeks, check for reports about problematic issues, and if all seems well, apply the update.
This build introduces a new PowerPoint feature: Notification emails for mentions, tasks, comments, and replies will now contain context previews even when the source document is encrypted, and the email will inherit the documentβs security policies.
This build fixes a bug in which users were seeing high CPU usage when typing in Outlook. It also includes a variety of security updates: see details.
What IT needs to know: Because this is a security update, it should be applied relatively soon. Over the next few weeks, check for reports about problematic issues, and if all seems well, apply the update.
This build fixes a wide variety of bugs, including one in which PowerPoint was unable to open a file from a network mapped drive from File Explore, another in which Word closed unexpectedly when opening .doc files, and another for the entire Office suite in which large 3D files couldnβt be inserted.
This build fixes a single bug in Word in which users may have encountered an issue with saving, seeing the message βsavingβ¦β in the title bar. ItΒ Β also includes a variety of security updates. GoΒ here for details.
What IT needs to know:Β Because this is a security update, it should be applied relatively soon. Over the next few weeks, check for reports about problematic issues, and if all seems well, apply the update.
This build lets you use Dark Mode in Excel, which darkens your entire sheet, including cells, and may reduce eye strain. It also fixes several bugs, including one in Word in which opening specific files that contain many tracked changes and comments resulted in poor performance, and one in PowerPoint in which the app was not displaying the icon for an inserted PDF object.
This build fixes several bugs, including one in which some Word files with numerous tracked changes and comments were slow. It also includes a variety of security updates: see details.
What IT needs to know: Because this is a security update, it should be applied relatively soon. Over the next few weeks, check for reports about problematic issues, and if all seems well, apply the update.
This build fixes a wide variety of bugs, including one in Word in which the default font size may not be 12pt as expected, and another in which PowerPoint automatically closed when the system went into hibernate or sleep mode.
This build removes the option to display Track Changes balloons in left margin in Word. It also includes a variety of security updates. See βRelease notes for Microsoft Office security updatesβ for details.
What IT needs to know: Because this is a security update, it should be applied relatively soon. Over the next few weeks, check for reports about problematic issues, and if all seems well, apply the update.
Across the stories today, a common thread emerges: conservation is working, but the planet isnβt waiting for us to catch up. From Kentβs butterfly meadows to Cambodiaβs tiger corridors, dedicated efforts are bringing species back from the brink β yet climate disasters are simultaneously accelerating faster than anyone predicted.
The Duke of Burgundy butterflyβs 90-fold population surge in Kent represents the kind of conservation victory that reminds us whatβs possible with focused effort and patience. Similarly, Kyrgyzstanβs massive wildlife corridor for snow leopards and Cambodiaβs ambitious tiger reintroduction program signal that countries are thinking beyond traditional protected areas toward landscape-scale solutions. These arenβt just feel-good stories β theyβre blueprints for how targeted conservation can reverse seemingly impossible odds.
But the dayβs coverage points to growing momentum around an uncomfortable truth: even our biggest successes are racing against accelerating climate impacts. In Indonesia, extreme rainfall killed 58 of the worldβs rarest orangutans in just four days β a 7% population loss that no conservation program can quickly replace. Meanwhile, Antarctica recorded winter temperatures above 15Β°C, shattering records and leaving scientists describing conditions as βvery strange.β
Behind the numbers are real communities adapting in real time. Indonesian fishers are turning to mangrove restoration and crab farming as traditional catches dwindle. Coffee farmers worldwide are rediscovering forgotten species as familiar varieties fail under changing conditions. In the Cotswolds, citizen scientists are filling gaps left by overstretched agencies, uncovering βworryingβ pollution levels in rivers that official monitoring might have missed.
The tension between protection and development threads through multiple stories today. Property developers argue that new environmental regulations will drive up housing costs, while environmental groups fight to prevent SpaceX from acquiring wildlife refuge land in Texas. In Ethiopia, successful conservation efforts are preserving nature but may be undermining local food security β a reminder that progress and pressure often arrive together.
Perhaps most revealing is how different institutions are responding to crisis. While the U.S. weakens marine protections domestically, itβs actively policing illegal fishing internationally. Kenya becomes the first African nation to receive UN climate disaster compensation, while proposed federal budget cuts threaten to eliminate Great Lakes monitoring programs. Chinaβs Belt and Road Initiative generates massive emissions through steel-heavy construction, even as solar power surpasses coal in the U.S. for the first time in history.
The enforcement stories offer a different kind of hope. South Africa sentenced two pangolin traffickers to eight years in prison β a serious consequence in a field often marked by weak penalties. Durhamβs chemical company faces state lawsuits for decades of toxic contamination, while an 80-year-old Texas shrimper traveled 8,000 miles to Taiwan to confront a petrochemical giant at their shareholder meeting.
What emerges is a picture of environmental action happening at every scale β from butterfly meadows to international courts β but also of systems under unprecedented stress. As extreme weather kills endangered species faster than breeding programs can replace them, and as climate displacement intensifies while immigration laws offer no protection, the question isnβt whether we can solve individual problems. Itβs whether we can solve them fast enough, and at the scale the planet now demands.
In 2011, miles of rock shifted deep underwater in the Japan Trench, causing an earthquake that deformed the seafloor and caused a devastating tsunami. Off the Eastern Coast of the TΕhoku region in Japan, a huge piece of the Earthβs crust carrying the Pacific Ocean, known as a tectonic plate, is forcing itself beneath Japan and into the Earthβs interior. Researchers think rock from this plate pushed against rock far beneath Japan, building pressure until it became too great. The lower plate slipped, spreading energy from the slip site and causing the earthquake.Β
Plate slip can cause 2 types of outcomes. The first occurs kilometers deep in the Earthβs crust, causing earthquakes too small to trigger tsunamis. The second type causes extreme slip events that begin deep in the crust, like the 2011 event that extended into the Japan Trench and warped the seafloor. The moving seafloor displaces seawater, causing a tsunami. These events are referred to as slip-to-the-trench style earthquakes.
Researchers think this phenomenon is not unique to 2011, as Japan has a long history of tsunami-causing earthquakes. Charlotte Pizer and colleagues investigated sediment from the Japan Trench to unearth the geologic history of slip-to-the-trench style earthquakes.
In between earthquakes, Japanese islands continuously shed sediment that fills the trench, forming horizontal layers. Slip-to-the-trench earthquakes bend and fold these layers. The team hypothesized that if they found these folds in the Japan Trench and dated them, they could catalogue the record of slip-to-the-trench style earthquakes in the area.
Earthquakes like these occur repeatedly, meaning that younger ones can erase folds caused by older ones. To account for this overprinting, the researchers chose a study site within the Japan Trench about 100 kilometers (60 miles) north of where the most severe earthquakes occur. This site is only mildly deformed by slip-to-the-trench earthquakes since itβs so far from their source, making it easier for the team to identify individual events.Β
Pizer and her group pieced together data collected from this site by previous researchers to reconstruct Japanβs earthquake history. They compiled 3 main types of data. Two of these were images of sediment layers in the trench constructed from reflections of vibrations sent into the ground, called seismic profiles.Β
The first seismic profile captured the full trench, over 1 kilometer deep (about 0.6 miles), at 5-meter (16-feet) resolution. Using this method, any layers smaller than 5 meters thick wonβt appear in the image. The second seismic profile captured only the top 40 meters (130 feet) of sediment, but could detect layers as thin as 10 centimeters (4 inches).Β
The final type of data they used came from a 36-meter (120-foot) long cylinder of sediment extracted from the bottom of the trench, called a sediment core. Researchers in the past tied layers within this sediment core to historic earthquake events. They showed that it recorded 2 specific earthquakes in the area, the Kyotoku earthquake of 1454 CE, and the Jogan earthquake of 869 CE, both of which likely caused tsunamis.Β
Pizerβs team could observe the depth of the Kyotoku and Jogan earthquake layers taken from the sediment core in their high-resolution seismic profile of the trench. In these high-resolution data, they noticed that deformation occurred in the sediment up to the layer marking the Jogan earthquake, but not above it, meaning deformation of the trench happened during this 869 CE event.Β
The high-resolution data were only able to image sediments from recent earthquakes since 869 CE, but the low-resolution profile, which imaged the full trench, was able to capture the deeper, older record. When they looked deeper into the trench sediment, the researchers noticed that deformation from the 869 CE event had spread from where the tectonic plate is colliding with Japan. They saw at least 6 more similarly deformed layers, implying each was its own slip-to-the-trench event, although the dates of these events are unknown.
Pizer and colleagues concluded that slip-to-the-trench earthquakes are long-standing, common events in the Japan Trench. They hope future scientists will continue to research this site to better assess tsunami risks in Japan.
When it comes to AI deployments, IT leaders are often caught in an awkward middle space, trying to reconcile conflicting directives from senior management with constantly changing AI models, capabilities, and costs; data governance and security needs; and the limitations of their own team.
βVery few real benefits can be attained by simply purchasing an AI product and giving it to employees. Vendors have been overselling that fallacy for the past three years,β said Nader Henein, a Gartner VP analyst.
βThe reality is that strong AI value and consistent ROI are almost always a result of deep and intentional integration of AI capabilities into existing workflows. For that you need specialized teams, which do not come cheap, and organizations have been recruiting those teams in a variety of ways,β Heinen said.
Among the options available to IT leaders looking for help with AI deployments are traditional IT consultancies, AI-specific consultancies, and independent contractors. Large enterprises with deep pockets can consider acquiring an AI firm and integrating its technology and expert staff. The use of open source to reduce vendor lock-in is a strategy that can sit on top of those others, an approach that Capital One has used.Β
But the option that has been getting the most attention recently is bringing in forward-deployed engineers (FDEs), teams of experts from AI vendors that embed with a customerβs in-house engineers to oversee AI rollouts within the enterprise environment. Both OpenAI and Anthropic have recently announced FDE offerings, for example, and Microsoft is partnering with consulting giant EY in a new FDE program for agentic AI deployments.
Engineering teams employed by AI vendors have key strengths, such as understanding their models better than anyone else, having experience integrating those models into different types of enterprise environments, and knowing about upcoming model capabilities before theyβre announced. But they also have the obvious drawback of vendor lock-in. Even if future rollouts are not within their contracted deliverables, those vendor employees could subtly influence a clientβs future AI efforts.Β
Flavio Villanustre, CISO for LexisNexis Risk Solutions, cautions IT executives to move into FDE programs carefully.Β
FDEs βare financially incentivized to grow customersβ use of a vendorβs AI products and to create stickiness with that vendorβs services,β he said. βWhile FDEs may be a reasonable value-added service by the AI vendor, customers should always find other unbiased expert opinions that can evaluate competitive solutions across multiple vendors.β
This is particularly important at a time when βinvestor-subsidized AI token business models are starting to show cracks,β Villanustre said. βAlso, in the current rapid pace of innovation in this field where AI vendors are constantly leapfrogging each other, retaining the agility to move from one vendor to the next could create significant competitive advantages.β
Analysts, consultants, and other industry experts who spoke with Computerworld about FDEs echoed Villanustreβs caution, citing concerns around hidden costs, confidentiality, observability, and vendor lock-in.
Long-term costs and vendor lock-in
A key issue that IT executives need to consider is how long the FDE teams will be needed.Β The enterprise will likely need an ongoing series of AI deployments synced with the current AI model(s). If help is needed today, why would that change tomorrow?
Enterprises tend to overlook those longer-term costs, said John Sangyeob Kim, an AI engineer at software development vendor Solidroad.
βDeployment is maybe 20% of the total cost. The other 80% is keeping the system running through model upgrades, data drift, and edge cases that only appear after months in production,β Kim said. βMost contracts price the first part and assume the rest. Deployment isnβt the hard part of enterprise AI anymore. The next eighteen months are.β
And whether itβs intentional or not, FDEs will naturally favor their own product portfolio β itβs what they know best.
βFDEs from model labs are good at making their own models work in your environment. They are less suited for multi-model systems, because their incentive is to keep you inside their ecosystem,β Kim said.
Sanchit Vir Gogia, chief analyst at Greyhound Research, said IT leaders should look at the FDE model as a strategy involving ongoing operational power.Β
βWhoever shapes the deployment pattern shapes the enterpriseβs future muscle memory. Whoever owns the evaluation layer owns the truth layer. Whoever controls the integration logic controls the dependency map,β Gogia said. βThis is why the FDE model matters. It is not just another delivery option. It is the frontier AI vendor moving closer to the customerβs workflow, operating model, and decision architecture.β
That proximity cuts both ways, Gogia noted. βFDEs are embedded inside the customerβs [environment], but they are also connected to the vendorβs commercial center of gravity. Their instinct will be to build around the model family, tooling assumptions, deployment patterns, and product roadmap they know best. This is perfectly natural. It is also precisely why CIOs must be cautious,β he said.
Allowing AI vendor employees an outsized say in enterprise deployment decisions could lock in model vendor dependency, which in turn will fuel high prices that canβt be fought effectively.
βFDEs can accelerate deployment and deepen dependency at the same time,β Gogia said. βFrontier AI vendors are no longer content to sell access to models. They increasingly want to shape how enterprises deploy intelligence. That is a larger prize.β
What happens when the FDE team leaves?
FDE post-departure risks are severe and often underappreciated, according to Justin Greis, CEO of consulting firm Acceligence and former head of the North American cybersecurity practice at McKinsey.
For one thing, the FDE team learns a massive number of operational details from the enterprise deployment. Although NDAs and confidentiality contracts protect any data accessed, they often donβt regulate observed processes and procedures.Β
βThe learnings are absolutely going to be taken from client to client,β Greis said. βWhoever helps deploy AI will learn far more than what appears in the statement of work. They will learn the real workflows, the undocumented exceptions, the data-quality gaps, the approval bottlenecks, the security workarounds, and the places where the business depends on a few people knowing what to do when the process breaks. That knowledge may be as sensitive and precious as the data itself.β
Another critical but often overlooked issue is how much meaningful control will IT have over the project if and when the FDE team leaves.
βThe danger is not using outside help. Most companies will need outside help,β Greis said. βThe danger is using outside help in a way that leaves the enterprise less capable and more dependent when the engagement is over.β
It is precisely those operational decisions that IT often neglects, said Solidroadβs Kim.
βThe best predictor of success is not the vendor. It is whether one internal engineer truly understands the system before the implementer leaves. What matters is who owns the evaluation loop after the demo,β Kim said.
βWhat happens to our prompts, scorers, and guardrails when the model version changes? If we paused this engagement tomorrow, what would actually stop working, by design or by accident?β Kim asked. βWhere do you want the enterpriseβs AI learning, control, and dependency to live after the engagement is over?β
Kim argues that observability β the ability to understand and manage all elements of a complex enterprise environment β is a critical function to which IT often gives insufficient attention. Determining whether the project uses the enterpriseβs observability stack or the vendorβs observability stack is crucial.
βIf the implementer is using their observability stack, that is fine during the build, but you need a plan to migrate it to something you own before they leave; otherwise the visibility walks out of the door with them,β Kim said. βIf they are using yours, that is the best case. It means they are working inside the system your team will operate long-term.β
A major problem crops up when they are using neither the enterpriseβs nor the vendorβs observability stack. βNeither means they are building the system without any production observability layer at all, and you inherit a system you cannot see into. The first time something breaks in production, you have no traces, no failure history, and no way to tell whether the issue is a model regression, a data problem, or a code bug,β Kim said.
βIf observability was not a priority during the build, evals and regression testing usually werenβt either, so you are inheriting a system you cannot measure and cannot safely change. Thatβs the worst possible handoff position,β he said.
Weighing the alternatives
While the FDE approach is not new, it is just now beginning a surge in popularity, and there are a finite number of such specialists available.Β That means not all companies even have the option of using FDEs.
This availability disconnect is especially prominent for non-US deployments, where on-site FDEs are rarer, said Gartnerβs Henein. βWhere is the development happening? There may not be FDEs available in that region,β he said.Β
There are plenty of other places enterprises can turn to for AI help. Ishraq Khan, CEO of coding productivity tool vendor Kodezi, encourages IT executives to consider a wide range of options but notes that all approaches have major drawbacks.
βTraditional consultancies are usually stronger at governance, process, compliance, and organizational coordination. They know how large enterprises operate politically and structurally. The downside is that many move slower and often lack deep frontier AI specialization,β Khan said.
Gogia from Greyhound Research put it more colorfully: Traditional IT consulting firms βknow how to get legal, risk, security, finance, HR, and business units into the same room without anybody setting fire to the carpet. For regulated enterprises, that matters,β he said.
Specialized AI consultancies have a different set of strengths, Khan said. βAI-native consultancies move much faster and are often more technically current, but many are still immature operationally. Some can build impressive demos without fully understanding long-term maintainability, governance, or production reliability.β
Greis from Acceligence commented on two other options for bringing in outside AI help. Using an independent contractor βcan be great for eval design, architecture reviews, red teaming, agent design, or getting a stalled team unstuck,β he said, but it can increase the risk of βkey-person dependency,β where a single external person is the only one who understands the system.
As for purchasing an AI firm and onboarding its employees, a practice known as βacquihiring,β Greis said it can work well when the AI capability and expertise being brought in are truly strategic for the acquiring enterprise. But there is a risk that the acquired team will be smothered by the parent companyβs bureaucracy: βYou buy a speedboat, bolt it to an aircraft carrier, and then wonder why it stopped moving,β he said.
Finally, an open-source strategy can give companies flexibility and reduce vendor dependence, but βmany companies underestimate the operational burden that comes with it,β Kodeziβs Khan said. βOpen source only helps if the organization has the internal talent and discipline to maintain it properly.β
Bottom line: enterprises need to define their true objectives before deciding on an approach. Khan offered several key questions for CIOs to consider: βWho owns the deployment after implementation? Can we move providers later without rebuilding everything? What happens if the vendor relationship changes or disappears? Are we optimizing for short-term deployment speed or long-term operational resilience?β
In any scenario where outside firms have direct access to enterprise systems, IT needs to be kept fully in the loop. βThe worst outcome is when an enterprise successfully deploys AI but no longer fully understands how its own systems operate underneath,β Khan said.
External help for AI deployments: 6 options
Pros
Cons
AI vendor FDEs
+Β Best expertise on the main model being used
βΒ Vendor lock-in
βΒ Operational detail leaks
Traditional IT consultancies
+Β Best understanding of change management, legacy integration, global rollout, governance, and operating-model redesign
βΒ Can be too slow, too expensive, or too generic
AI consulting firms
+Β More practical AI deployment experience than traditional consultants
+Β Less vendor lock-in than model-provider FDEs
βΒ May not sufficiently understand enterprise-grade requirements: security, identity, auditability, compliance, incident response, cost controls, and long-term maintainability
Independent contractors
+Β Useful for precision tasks: eval design, architecture reviews, red teaming, agent design, or getting a stalled team unstuck
βΒ Risk of βkey-person dependencyβ
βAcquihiringβ an AI firm
+Β Works when the acquired capability is truly strategic
βΒ Acquired team can be smothered inside existing bureaucracy
Deploying open-source products
+Β Reduces dependency on one model vendor
+Β Attractive for data sovereignty, control over enterprise systems, cost efficiencies, and regulated environments
βΒ Enterprise takes on full responsibility for security, patching, evaluation, deployment, monitoring, and lifecycle management
A talk on rising energy costs on Capitol Hill hosted by Democrats, from left, Sen. Martin Heinrich of New Mexico, Senate Minority Leader Chuck Schumer and Sen. Sheldon Whitehouse of Rhode Island, in March.
The Met Office has claimed a new Welsh temperature record for springtime. But it was recorded at Bute Park, a Class 5 junk site where hot air is frequently vented from greenhouses, says Paul Homewood.
The southern lights, also known as the aurora australis, were captured by the NASA astronaut Jessica Meir from the International Space Station on Saturday.
Compare NotebookLM with Notion, Obsidian, Recall, Atlas, and Open Notebook to find the best AI research and knowledge management tool for your workflow.
The four astronauts named to the Artemis 3 crew are all male, but NASA officials emphasized they were selected based on their qualifications and experience.
Chinaβs Belt and Road Initiative, the worldβs largest infrastructure development program, is generating enormous greenhouse gas emissions that threaten global climate goals. Two comprehensive new studies reveal that more than half of the programβs carbon footprint comes from a single source: steel production, with the vast majority manufactured within China itself.
The Belt and Road Initiative spans over 130 countries and involves massive construction projects including highways, railways, ports, and power plants across Asia, Africa, and Europe. While these infrastructure developments promise economic growth and connectivity, the environmental cost is staggering. The steel required for bridges, buildings, and transportation networks carries an enormous carbon burden, as steel production is one of the most energy-intensive and polluting industrial processes.
The research highlights a critical challenge in global climate action: even as countries commit to reducing emissions, mega-infrastructure projects continue pumping massive amounts of carbon dioxide into the atmosphere. Steel manufacturing typically relies on coal-fired furnaces and generates substantial emissions both from energy consumption and chemical processes that release CO2 directly from raw materials.
Addressing this climate impact will require fundamental changes in how infrastructure projects approach materials and manufacturing. The studies emphasize that stronger environmental regulations and major investments in cleaner steel production technologies are essential. Without these shifts toward low-carbon manufacturing methods, large-scale construction projects will continue undermining global efforts to limit temperature rise and avoid the worst impacts of climate change.
NASA's Artemis 3 mission in 2027 looks to be one of agency's most complicated missions ever, with three giant rocket launches and two private moon lander prototypes that haven't been built yet.
Login
