News
- Amazon has rolled out tougher DRM to the Kindle Oasis
- The same update has previously landed on most other Kindle models
- The company has also closed an airplane mode loophole for Libby loans
If you like reading Kindle books on other devices or borrowing digital library books using Libby, Amazon has just made some changes that you’re unlikely to be happy about.
First up, as reported by The eBook Reader, a software update has rolled out for the Kindle Oasis that adds a new hardened DRM (Digital Rights Management) to books on it, meaning that most DRM-removal tools will no longer work.
While we don’t condone piracy, there are legitimate reasons to want to remove DRM, such as reading the book on a non-Amazon ereader that doesn’t have access to the Kindle app.
And this isn’t the first or only Kindle to get this undesirable update — now, the only supported model that doesn’t have this new DRM is the Kindle Voyage, and it’s probably only a matter of time before that gets it too.
The Amazon Kindle Oasis (Image credit: TechRadar)No more lengthy loansThe other change that Kindle users are unhappy with is that you can seemingly no longer keep a Libby book beyond its due date by turning airplane mode on. This was a handy workaround that gave you more time with a borrowed book, but now Reddit users report being prompted to turn Wi-Fi on to access their loans.
As these are digital loans, this workaround wasn’t really hurting anyone — the books would still be made available to other users after the loan period expired anyway; you’d just also still have a copy on your Kindle.
Unsurprisingly, the online reactions to these changes aren’t positive, with Reddit comments about the new DRM including the likes of “glad I switched to Kobo,” while of the Libby change, one commenter claimed it was “my biggest nightmare.”
If you’re affected by either of these issues, then there aren’t any easy solutions — other than potentially switching to another brand. In the case of the DRM, Kobo books currently use a version that’s easier to remove, but even on Kobo, the airplane mode loophole won’t work.
- Microsoft Teams is changing how it displays swear words
- The toggle to hide bad words is now Off by default
- However Government users will have to wait a little longer, for an unknown reason
Frustrated Microsoft Teams users finally be able to express their true feelings after the company revealed changes to how it censors profanity in captions - although not all users will be able to "benefit" just yet.
In an updated message center post, Microsoft outlined the changes coming to its profanity filter for Teams, noting that the default setting for live captions has now been switched from On to Off.
However this doesn't yet apply to all users, as Government officials and staff will have to wait a little while longer, with their rollout deadline now extended until sometime at the end of August 2026.
Safe for workMicrosoft first introduced the profanity toggle in 2023 in a bid to cut down on bad language in Teams Live Captions by replacing any swear words with asterisks.
Originally, it was up to the user whether to leave the toggle on, rather than the meeting organizer or admin - but in May 2026, Microsoft appears to have changed its mind for some reason, and opted to disable the "profane words" filter by default.
"This change ensures captions more accurately reflect spoken content, supporting accessibility needs and aligning with regional regulatory requirements (including the EU)," the company wrote.
Microsoft added that users retain full control and can enable or disable the filter at any time, but, somewhat tongue in cheek, notes that, "No admin action is required, but informing support teams and users is recommended."
The delay will apply to Government Community Cloud (GCC), GCC High, and US Department of Defense users, who often face extra complications due to security checks and operational reasons - although Microsoft offered no clues as to why that is the case here.
The news is the latest in a series of recent updates seemingly geared towards helping Microsoft Teams users show off how great they are.
This includes bringing "Badges" to your Microsoft Teams profile card, allowing users to display all their achievements to anyone who cares to look.
It is also working on a feature which will automatically update a user's work location when they connect to an office Wi-Fi network - hopefully meaning less confusion about where workers actually are situated, but bad news for those looking for a quiet day in the office tucked into a corner.
Via The Register
Motorways don't stay safe simply because drivers follow the Highway Code. They rely on speed limits, lane markings, and crash barriers that keep traffic moving to help prevent mistakes from becoming serious accidents.
AI governance works the same way. Policies define the rules, but operational controls keep organizations on course when technology, users, and risks change.
As organizations accelerate AI adoption, many have focused on developing policies, governance frameworks, and acceptable use guidelines. Those are essential first steps. But policies alone can't prevent AI systems from accessing the wrong data, interacting with the wrong applications, or creating unintended operational risks.
The EU AI Act has made AI governance a board-level issue, requiring organizations that use or develop AI to identify, manage, and document risks, particularly for high-risk systems.
This has introduced new expectations around oversight, documentation, data governance, and transparency. However, regulation alone won't solve the biggest practical challenge: AI adoption is moving faster than governance.
Employees are using public AI tools, developers are relying on coding assistants, and business teams are deploying AI capabilities across existing platforms. In many cases, these technologies are introduced before security, compliance, and risk teams fully understand what they can access, which systems they influence, or how they change the organization's overall risk profile.
That's the gap between regulatory ambition and operational reality. Organizations may have approved AI use cases and governance frameworks, but they're often governing only part of the AI already operating across the business.
Closing that gap starts with treating AI as an operational challenge rather than simply a compliance exercise. In practice, moving beyond policy means understanding how AI is used, applying controls according to business risk, and adapting governance as AI capabilities evolve.
Shadow AI is changing the governance challengeTraditional governance assumes organizations know what technologies are operating across the business. AI has changed that. Shadow AI is no longer limited to employees experimenting with public tools.
It also includes embedded AI capabilities introduced through routine software updates, AI-powered workflows created by business users, and autonomous agents operating across enterprise systems without ever being treated as formal AI projects. These capabilities are often adopted faster than governance processes can identify, assess, and manage them.
Today, AI isn't simply supporting employees - it's acting on their behalf. AI agents can retrieve information, trigger workflows, interact with enterprise systems, and make operational decisions using permissions inherited from the people or systems they represent.
Because of this, the enterprise attack surface has fundamentally changed. Security teams are no longer protecting only people, devices, and applications - they're also securing autonomous systems capable of moving across environments, accessing sensitive information, interacting with critical workflows, and making decisions independently.
Every new AI agent represents another potential pathway for accidental misuse or malicious activity if it isn't governed appropriately.
Regulation defines the rules. Context builds the rails.The EU AI Act places significant emphasis on accountability, oversight, and risk management throughout the AI lifecycle. But meeting those expectations requires far more than documentation.
Regulation defines the outcomes organizations must achieve; the challenge is translating those requirements into operational governance across environments where AI is constantly evolving.
That starts with understanding AI in context. Risk can't be assessed by looking at an AI system in isolation. An AI assistant summarizing internal documents may appear relatively low risk until it gains access to commercially sensitive information.
Likewise, an AI agent automating procurement may operate safely under normal circumstances, but its risk profile changes significantly if it can approve financial transactions, inherit privileged identities, or initiate actions across critical business systems.
Risk is defined not only by the AI itself, but by the identities, applications, infrastructure, data, and business processes it connects to. As it becomes more deeply embedded across these interconnected systems, AI governance increasingly overlaps with cybersecurity.
Every AI capability introduced into the enterprise can create new attack paths, expand access to sensitive information, and increase the number of non-human identities operating across the environment.
Recent incidents, such as PocketOS’s database being wiped by an AI coding agent in seconds, have shown how quickly AI risk can become operational risk when AI systems are granted more authority than intended.
Organizations should therefore govern AI identities and permissions with the same rigor as human users, regularly reviewing inherited access and removing unnecessary privileges before they create new attack paths.
Governance also needs to extend beyond individual AI systems. Organizations should understand how AI interacts with identities, enterprise assets, business processes, and critical data so they can prioritize controls where they'll have the greatest impact.
Bringing security, risk, compliance, and technology teams together around this shared understanding turns governance into an enabler of resilience rather than simply a compliance exercise.
Building the railsAs AI regulation continues to evolve, organizations will be expected to demonstrate that governance exists not only on paper, but in practice. Policies establish the rules, but operational governance builds the rails that keep AI operating safely as technologies evolve, permissions change, and new capabilities emerge.
Moving beyond policy means embedding governance into day-to-day operations. Organizations should continuously identify new AI capabilities, understand how they relate to enterprise assets, review the permissions they inherit, assess business impact, and prioritize the exposures that present the greatest risk.
This allows teams to apply controls where they'll have the greatest impact while supporting responsible AI adoption across the business.
Governance also needs to keep pace with change. As AI agents evolve and environments shift, organizations should be able to adjust permissions, restrict access, isolate affected agents, or prevent actions that exceed an AI system's intended role before they become wider operational issues.
The objective isn't to slow AI adoption, but to create the confidence to innovate securely as AI becomes part of everyday business.
Innovation needs both rules and railsAI will continue to transform how organizations operate, innovate, and compete. But organizations that realize AI's full potential won't be those with the longest policy documents.
They'll be the ones that embed governance into everyday operations, govern AI identities and permissions with the same discipline as any other critical asset, and continuously adapt controls as technology evolves.
The EU AI Act has raised expectations around accountability, but organizations that move beyond policy and compliance will be best placed to unlock AI’s full potential.
In the age of autonomous AI, governance isn't just about setting the rules - it's about creating the guardrails that let organizations innovate with confidence without compromising security, trust, or resilience.
We've featured the best AI website builder.
This article was produced as part of TechRadar Pro Perspectives, our channel to feature the best and brightest minds in the technology industry today.
The views expressed here are those of the author and are not necessarily those of TechRadarPro or Future plc. If you are interested in contributing find out more here: https://www.techradar.com/pro/perspectives-how-to-submit


