Acest browser nu mai este acceptat.
Faceți upgrade la Microsoft Edge pentru a profita de cele mai noi funcții, actualizări de securitate și asistență tehnică.
Sfat
When reading about cloud native endpoints, you see the following terms:
Organizations are focusing on supporting remote and hybrid workers. With cloud-native endpoints, organizations can:
In this set of articles, you will:
✅ Learn about cloud-native endpoints and the benefits to organizations and end users (this article).
✅ Step through a tutorial that creates a Windows device that's cloud-native:
✅ Learn more about the Microsoft Entra concepts that are part of cloud-native endpoints, including accessing on-premises resources:
✅ Get guidance and advice on moving your workloads and your organization to become cloud-native:
✅ Read about some scenarios that can affect your cloud-native migration:
Cloud-native endpoints are devices that can be deployed from anywhere. They receive their applications and configurations dynamically from the cloud, and can easily be reset or restored.
A cloud-native endpoint doesn't necessarily live exclusively in the cloud. Instead, any endpoint that's cloud-native eliminates hard dependencies to on-premises connectivity and on-premises resources.
These endpoints can be located anywhere that has internet access. They can also be physical devices or virtual machines.
From a technical perspective, cloud-native endpoints are Windows devices that are deployed using Windows Autopilot, joined to Microsoft Entra (Microsoft Entra joined devices), and are automatically enrolled in a Mobile Device Management (MDM) solution, like Microsoft Intune.
A cloud-native endpoint has the following characteristics:
For end users, they only need an internet connection. Their data and critical settings can be automatically preserved and restored using Enterprise State Roaming, or similar solutions. If end users experience issues during deployment or at any time, then they can reset and reprovision the device without contacting support.
Microsoft recommends that organizations focus on adopting cloud-native endpoints.
Cloud-native endpoints provide many benefits to end users and IT:
Best for remote workers
End users don't worry about connecting to the VPN or other networks. They sign in to devices from anywhere, and run actions, like password reset, without connecting to on-premises AD.
Microsoft Entra joined endpoints do the initial sign-in using an internet connection. The Microsoft Entra joined sign-in process doesn't use an on-premises domain controller for connectivity, and is faster than a traditional domain-based sign-in.
Traditional domain joined PCs require connectivity to domain controllers for initial sign-in.
Deploy from anywhere
To deploy new devices, administrators can be anywhere with an internet connection. You can provision or reset devices, and have the devices ready quicker than traditional provisioning, possibly in minutes. The reliance on on-premises resources is reduced, which simplifies the endpoint requirements and endpoint management.
Simplified management for all platforms
Users and administrators get a unified management experience for all platforms, including Android, iOS/iPadOS, macOS, and Windows. With Intune, you can manage mobile and non-mobile devices and operating systems. You don't need to rely on complex group policy management.
Provide a secure Single-Sign-On (SSO) experience to cloud and on-premises apps
Cloud-native endpoints include native single sign-on (SSO) for cloud and on-premises resources, such as file servers, print servers, and web applications.
Secure access without passwords
With Windows Hello for Business, end users can sign in to their device, and access resources without passwords.
For more specific information, go to Password-less Strategy.
Seamless experience for documents, settings, and preferences
With OneDrive, end users automatically gain access to their documents, can restore any previous Office and Windows settings, and avoid spending time recovering data.
For example, you can store the following user data on OneDrive:
When user data is stored on OneDrive, it can synchronize the data with all user endpoints.
The High level planning guide to move to cloud-native endpoints is a good resource. It covers the following areas:
Plan: When ready to move to cloud-native endpoints, organizations focus on several key areas:
For more specific information, go to the High level planning guide to move to cloud-native endpoints.
Create a Proof of Concept: Do an initial proof of concept (POC). The goal is to understand changes and their impact.
For more specific information, go to the High level planning guide to move to cloud-native endpoints.
Instruire
Modul
Secure endpoints with Zero Trust - Training
Learn how to use Zero Trust to secure endpoints to protect your organization and its users.
Certificare
Certificat Microsoft 365: Asociat administrator punct final - Certifications
Planificați și executați o strategie de implementare a punctelor finale, utilizând elemente esențiale ale gestionării moderne, abordărilor în cooperare și integrării Microsoft Intune.
Documentație
Update your workloads to support cloud-native endpoints - Microsoft Intune
To support hybrid and remote workers, convert or migrate your workloads to support cloud-native endpoints. This planning guide focuses on deploying apps and updates with Intune, moving from Group Policy Objects, and using Windows Autopilot.
Tutorial-Get started with cloud-native Windows endpoints - Microsoft Intune
Set up secure cloud-native Windows endpoints that are Microsoft Entra joined, enrolled in Intune, and then deploy at scale with Windows Autopilot.
Common issues and resolutions with cloud-native endpoints - Microsoft Intune
Learn more about the known and resolutions when using cloud-native endpoints. Use user-based authentication; don't use machine authentication. Existing group policy objects might not apply.