Quelle: Link
Microsoft Word: Retirement of legacy compatibility settings
Quelle: Link
Microsoft Word: Retirement of legacy compatibility settings
Quelle: Link
Today, we’re announcing that Claude models by Anthropic in Microsoft Copilot are coming into the EU Data Boundary, strengthening model choice for organizations across Europe. This means customers will no longer need to choose between access to Claude models and the Microsoft regional data-processing commitments they rely on. By the end of 2026, organizations in the European Union (EU) and the European Free Trade Association (EFTA) will be able to use Claude models across Copilot experiences, including Copilot Cowork, with processing within the EU Data Boundary, where their data is already stored.
The EU Data Boundary is Microsoft’s own industry-leading commitment to store and process data for Microsoft 365 and other online services within the EU and EFTA. It goes beyond current regulatory requirements and is built on Microsoft’s comprehensive portfolio of compliance offerings and certifications.
For eligible Microsoft 365 customers in the EU and EFTA, it’s included in our contractual terms, with no opt-in or additional purchase needed. EU Data Boundary commitments reflect Microsoft’s principles of transparency, accountability, and data protection. Organizations that need more granular control can also store Microsoft 365 data at rest in their own country with in-country data residency, available in 10 countries in the EU and EFTA.
Claude models will join other leading models, including Microsoft-operated models, already processing data within the EU Data Boundary. This helps organizations, including those in regulated industries and the public sector, address their compliance requirements as they scale the latest AI solutions across their organization.
Copilot brings leading models from Anthropic and other providers into one governed experience grounded in your work, so your people can match the right model to the task at hand. Claude models already power work across Copilot experiences such as Chat, Copilot in Microsoft 365 apps, Copilot Cowork, and Copilot Code.
Claude models in Copilot are covered by Microsoft’s enterprise data protection, customer data isn’t used to train generative AI foundation models, and admins decide who can use them, so organizations can take advantage of model choice with consistent security, compliance, and governance.
Organizations already using Claude models in Copilot won’t need to take any action. Once available, processing for these models will move into the EU Data Boundary automatically.
Organizations that haven’t enabled Claude models yet can turn them on at any time, with processing moving into the EU Data Boundary once available. The setting is disabled by default in the EU and EFTA, and admins can enable it for all users or for selected users and groups in the Microsoft 365 admin center. For details, see Claude models in Microsoft Online Services on Microsoft Learn. We’ll share more details as we get closer to availability.
AI is moving fast, and the best model for a task can change. Copilot gives organizations one governed experience for adopting leading models as they evolve, with familiar security, compliance, and administrative controls. Extending the EU Data Boundary to Claude models is the next step. For organizations across Europe, this means the latest AI in Copilot, with the data commitments they trust.
Learn more about the EU Data Boundary and AI models in Microsoft Copilot.
Link: Quelle
Starting November 2, 2026, usage-based billing will be enabled by default for new Microsoft 365 Copilot Business licenses purchased through Cloud Solution Providers (CSP). Pay-as-you-go will be the default billing configuration to help customers access eligible usage-based experiences, including Copilot Cowork, Work IQ APIs, and GitHub Copilot Harness, with less billing setup, while also providing flexibility to expand usage over time, based on business needs.
Resources
Quelle: Link
Office 2021 folgt der Modern-Lifecycle-Richtlinie.
Dies gilt für die folgenden Editionen: Home and Business, Home and Business für Mac, Home and Student, Home and Student für Mac, Professional
Die Supportzeiträume werden in Pacific Time (PT) für Redmond (Washington, USA) angegeben.
| Auflistung | Startdatum | Deaktivierungsdatum |
|---|---|---|
| Office 2021 | 5. Okt. 2021 | 13. Okt. 2026 |
Quelle: Link
As identity attacks grow more sophisticated in the AI era, organizations need stronger authentication methods that protect users from phishing, credential theft, and social engineering. To address these evolving threats, Microsoft Entra ID is updating its authentication experience by making passkeys the default phishing-resistant authentication method, helping customers reduce reliance on phishable methods such as SMS and voice.
Beginning September 1, 2026, Microsoft will begin rolling out passkeys as the default authentication experience in Microsoft Entra ID. As the rollout reaches each organization, users enabled for SMS or voice authentication will automatically be enabled for passkeys, and the next time they perform multifactor authentication, they’ll be prompted to register a passkey.
Following this transition, on February 1, 2027, Microsoft will retire Microsoft-provided telecom delivery for SMS and voice authentication and will no longer offer SMS and voice as a native Microsoft Entra capability. Organizations that still require SMS or voice authentication methods will have the option to choose one of our telecom partners through the Microsoft Security Store. Customers will be responsible for any associated telecom-related costs charged by the telecom partners.
We strongly recommend moving users to passkeys or another phishing-resistant authentication method as soon as possible.
| Date | Milestone |
|---|---|
| September 1, 2026 | All users enabled for SMS or voice are auto-enabled and nudged for passkey registration upon multifactor authentication sign-in.
Use the passkey deployment guide to prepare your environment for passkey use. Notify affected users about the upcoming change. Ensure every user has a phishing-resistant authentication method, such as a passkey, Entra passkeys on Windows, or a FIDO2 security key. |
| September 18, 2026 | Pricing, commercial terms, and a list of supported telecom providers will be shared.
If you plan to continue using SMS or voice authentication, review the available provider options and identify affected users. |
| October 30, 2026 | Admins may select and configure a supported telecom provider through the Microsoft Security Store. |
| February 1, 2027 | Microsoft-provided SMS and voice authentication ends.
If SMS or voice remains necessary for specific users, configure a supported telecom provider before this date. |
| After February 1, 2027 | Users who use SMS or voice for multifactor authentication will be required to register a passkey before they can sign in. Automatic prompts to register a passkey will be enforced for all users in all tenants. There will be no opt-out option. |