Tag: Microsoft

  • Hundreds Storm Microsoft Data Centre Site in Amsterdam

    Hundreds Storm Microsoft Data Centre Site in Amsterdam

    Several hundred activists opposed to the construction of a Microsoft data centre in Amsterdam occupied the site on Friday, in the opening action of a two-day protest against large data centres across Europe.

    The activists, from the collective Geef Tegengas, which campaigns for climate and justice, and the environmental group Fossielvrij, entered the construction site in the Sloterdijk district of the Dutch capital, halting work for the day.

    They reached the site by scaling barrier fences despite a police presence, and once inside they shouted political slogans and sprayed anti-Microsoft messages on walls under construction, according to reports from the scene. Some climbed a construction crane and set off flares.

    A Reuters witness counted about 100 people breaching the site’s boundaries, while a spokesperson for Geef Tegengas told local broadcaster AT5 that around 500 demonstrators had entered the grounds, with hundreds more outside. Dutch news agency ANP reported that police arrested between 150 and 200 protesters on suspicion of trespassing, while other activists left the site voluntarily.

    Geef Tegengas spokesman Nathan Timmer told AFP the protest brought together many struggles in one place. He argued the finished centre would use as much electricity as all the households in Amsterdam combined and a huge amount of water. The group also objects to what it says is Microsoft’s role in supplying technology to the US immigration agency and the Israeli military.

    Microsoft said it respects the right to express views peacefully but does not condone actions that are unlawful or put people’s safety at risk.

    The site, in Amsterdam’s Westpoort port area, is being built by British developer Pure Data Centres as a campus of three towers about 85 metres tall, with Microsoft reported to be its sole tenant. The developer puts its capacity at 78 megawatts.

    AI data centres need large amounts of electricity, putting pressure on power grids that are often still reliant on fossil fuels, and in many cases large volumes of water to cool hot computing equipment. Opposition to their environmental impact is growing worldwide, alongside concerns about noise, pollution, their appearance and how many jobs they actually create.

    A coalition of campaign groups called Stop Dirty Data Centres has been pushing for a pause in the construction of such sites, and called for action on Friday and Saturday in European countries, with further protests planned in Denmark, Dublin and Warsaw.

  • AI Training Opt-Out: One Shared Robots.txt Rule

    AI Training Opt-Out: One Shared Robots.txt Rule

    Google, Microsoft and OpenAI have announced plans to honour a single shared robots.txt line that lets a website state its AI training preference once, instead of writing separate rules for each company’s web crawler. The move, reported on 1 November, could simplify life for publishers who want to keep their content out of generative AI training.

    At present, a site that wants to refuse AI training must write different rules for different crawlers, such as Google-Extended, GPTBot and others. Under the new approach, a site would write one ordinary rule group under a policy token called __usage_ai-training, using the familiar Allow and Disallow lines. An example in the proposal blocks an entire site except for its press-kit folder.

    The line comes from an Internet Draft submitted on 30 October by Kevin Kelley of Anthropic to the AI Preferences working group at the Internet Engineering Task Force (IETF). The draft is listed as an individual submission, which means it does not represent official IETF standardisation activity, and it is set to expire on 3 May 2027 unless a new version is published.

    How the shared signal works

    The draft adds no new directive to robots.txt. It reuses the file’s existing structure, but instead of naming a crawler on the User-Agent line, it names the policy token. The draft defines AI training as using content to modify a generative model’s learned parameters, and it says models that only do non-generative work, such as classification or ranking, are exempt.

    There are important limits. A wildcard group, written as User-Agent with an asterisk, can never match the token, and a robots.txt file with no __usage_ai-training group signals no preference at all. The token is also a statement about how content may be used, not an instruction about crawling itself, so it does not stop a crawler from visiting a site.

    Different timelines for each company

    Based on the timelines the companies gave, none of the three currently supports the shared line yet. Google aims to support it in early 2027, and says that where a site opts out through the shared line without specifying Google-Extended, it will treat that as if the publisher had disallowed Google-Extended, a control covering future Gemini model training and grounding in Gemini Apps and on Vertex AI.

    Microsoft will begin honouring the new options as it crawls from 1 February 2027, and will stop recognising its NoArchive and NoCache tags as training or grounding signals after 1 March 2027. It is also adding a separate page-level AI Grounding preference, which can be set by a meta tag or an HTTP header, with a DisallowExtended option that limits grounding to Microsoft’s own tools.

    OpenAI aims to honour the signal within the next few months, while its current robots.txt policy stays in effect. Anthropic, whose engineer wrote the proposal, has said it has already started building support. Microsoft has also warned that blocking AI grounding will significantly reduce a site’s visibility in AI-generated experiences, and that the new preferences do not establish licensing or payment arrangements.

    For publishers, the appeal is simplicity: one line, recognised by several companies, instead of a patchwork of crawler-specific rules. The open question is how consistently the companies will interpret that line once support actually arrives.

  • Windows 11 adds phone controls to Quick Settings

    Windows 11 adds phone controls to Quick Settings

    Microsoft is testing a new way to manage a connected phone from Windows 11, bringing phone controls and an internet speed test directly into Quick Settings. The features are part of Windows 11 Insider Preview Experimental build 26340.9767, released on 23 October 2026, and are rolling out gradually to testers.

    The headline change is a new Mobile devices experience in Quick Settings. With a supported Android phone connected, users can turn on Do Not Disturb before a meeting, change the phone’s ringer mode, and play a sound to find the phone nearby, all without opening a separate app. Opening Quick Settings from the taskbar and selecting Mobile devices shows the phone’s battery status and the controls available for that device. If no phone is connected yet, Windows walks the user through setup.

    Microsoft says the initial experience gives Android phones the most complete set of controls, while iPhone support starts with a more limited, status-focused experience. Capabilities can also vary by phone model and device configuration, so not every connected handset will show the same options.

    The idea is a small but practical one: the panel people already use for quick Windows actions becomes the place to silence a phone before a meeting or track it down when it slips down the side of the sofa. It builds on years of Microsoft’s Phone Link work, but moves the most common actions one click closer.

    Alongside the phone controls, the same build adds a built-in internet speed test to Quick Settings. Users can start a test from the new Speed test Quick Setting, from the Wi-Fi or Cellular flyout, or by right-clicking the network icon in the system tray and choosing Test internet speed. While the test runs, Quick Settings shows its progress, and the results, including download speed, upload speed and ping, appear directly in the panel.

    That matters because an earlier Windows Insider speed test sent users to a browser to see their results. The new version keeps everything inside Windows, giving a quick read on how the current connection is performing without breaking the user’s workflow. Microsoft notes that the test runs against the active internet connection, so it reflects the network in use at that moment.

    The build also adds the ability to filter Feature flags by enablement state on the Windows Insider Program settings page, a change aimed at testers rather than everyday users. Other additions in the release include an option to manage Microsoft 365 recurring billing from Settings, improved File Explorer loading indicators for slower locations such as network drives, and additional language support for mathematical content in Narrator.

    As with all Experimental channel features, there is an important caveat: these additions are in testing and may change or never reach the general release. The rollout is gradual, so Insiders on build 26340.9767 who do not yet see the Mobile devices section may simply not be in the rollout group yet. Microsoft has not said which phone models are supported or when the features might reach all Windows 11 users, but for testers, the phone is now one click closer to the desktop.