하나의 정책을 하나 이상의 기기에 적용할 수 있습니다. 그러나 한 장치는
단일 정책으로 설정할 수 있습니다
기기를 등록하는 동안 기기가 정책과 연결되어야 합니다. 해야 할 일
등록을 만들 때 policyName를 포함합니다.
토큰을 사용합니다.
기기가 다음에 연결된 policies 리소스 등록 토큰으로 등록됩니다.
policyName는 기기에 따라 기기 또는 직장 프로필에 적용됩니다.
프로비저닝 방법
있습니다.
정책 없이 등록된 기기는 정책이 사용 설정될 때까지 모든 기능에서 차단됩니다.
적용됩니다. 5분 이내에 정책이 적용되지 않으면
실패하고 기기가 초기화됩니다.
엔터프라이즈의 기본 정책 설정하기
정책 없이 기기가 등록되지 않게 하려면
엔터프라이즈의 기본 정책입니다. 이렇게 하려면 지정된 name
기본 정책을 "default"로 설정합니다. 그러면 이 정책이
다른 policyName이 지정되어 있지 않은 한 기본적으로
등록 토큰을 재설정해야 합니다.
지정되지 않은 값
_UNSPECIFIED 값은 비어 있거나 설정되지 않은 정책을 나타내는 데 사용됩니다. 이
관련 API 문서에서 정책이 적용되었을 때의 기본 동작을
명시적으로 설정되지 않았습니다.
일반적으로 Google에서는 필요한 경우를 제외하고는 기본 동작을 변경하지 않습니다.
보안상의 이유로 또는 Android 플랫폼의
변경사항에 맞춰야 합니다 YouTube에서는
그러한 변경이 예상되는 경우 EMM 커뮤니티에 사전 알림을 제공합니다.
EMM 및 관리자가 그에 따라 정책을 조정할 수 있습니다.
참고: 세분화된 정책을 사용 설정하려면 기기당 하나의 정책을 정의하는 것이 좋습니다.
기기 수준 관리 기능을 제공합니다. 기기 수준이 필요하지 않은 경우
AM API는 단일 정책을 여러 조직에 걸쳐 공유할 수 있도록 지원합니다.
기기에서 사용할 수 있습니다. 사용 선택과 관계없이 자동 패치 전파가 이루어집니다.
단일 정책을 설정할 수 있습니다
[null,null,["최종 업데이트: 2025-07-26(UTC)"],[[["\u003cp\u003eAndroid Management API utilizes \u003ccode\u003epolicies\u003c/code\u003e to manage device and app settings, allowing for the creation and application of tailored configurations to devices.\u003c/p\u003e\n"],["\u003cp\u003eDevices should be assigned a policy during enrollment, either through a specified \u003ccode\u003epolicyName\u003c/code\u003e in the enrollment token or by leveraging a default enterprise policy named \u003ccode\u003e"default"\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003ePolicies can be updated via \u003ccode\u003eenterprises.policies.patch\u003c/code\u003e, affecting all associated devices, while changing a device's policy requires using \u003ccode\u003eenterprises.devices.patch\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eAlthough a single policy can be shared across multiple devices, using one policy per device offers more granular control and is recommended for enhanced management capabilities.\u003c/p\u003e\n"],["\u003cp\u003eUnset policies are represented by \u003ccode\u003e_UNSPECIFIED\u003c/code\u003e values, and while default behaviors are generally stable, it's advisable to explicitly define critical policies for predictable results.\u003c/p\u003e\n"]]],["Policies in the Android Management API manage device and app settings. Create or update policies using `enterprises.policies.patch`, and delete them with `enterprises.policies.delete`. Apply policies to devices during enrollment by including the `policyName` in the enrollment token. Devices without a policy are blocked until one is applied; enrollment fails after five minutes without a policy. Set a default enterprise policy with `name` as \"default\". Update policies with `enterprises.policies.patch`, or change a device's policy with `enterprises.devices.patch`.\n"],null,["# Create a policy\n\n[`policies`](/android/management/reference/rest/v1/enterprises.policies) (also\ncalled a *policy*) are the core resource of the Android Management API. You use\nthem to create and save groups of device and app management settings for your\ncustomers to apply to devices.\n\n- To create or update a `policies` resource, call [`enterprises.policies.patch`](/android/management/reference/rest/v1/enterprises.policies/patch).\n- To delete a `policies` resource, call [`enterprises.policies.delete`](/android/management/reference/rest/v1/enterprises.policies/delete).\n\nSee example policies\n--------------------\n\nWe've created several examples of recommended policies for different device\nsetups and scenarios:\n\n- [Devices with work profiles](/android/management/policies/work-profile)\n- [Fully managed devices](/android/management/policies/fully-managed-devices)\n- [Dedicated devices](/android/management/policies/dedicated-devices)\n- [Network configurations](/android/management/configure-networks)\n\nApply a policy to devices\n-------------------------\n\nA policy can be applied to one or more devices. However, a device can only have\na single policy at any given time.\n\nA device should be associated with a policy during device enrollment. To do\nthis, include the `policyName` when [creating an enrollment\ntoken](/android/management/provision-device#create_an_enrollment_token). After a\ndevice is enrolled with the enrollment token, the `policies` resource linked to\nthe `policyName` is applied to the device or work profile, depending on the\n[provisioning method](/android/management/provision-device#provisioning_methods)\nused.\n| **Key Point:** A `policies` resource not linked to any device or enrollment token for over seven days may be deleted automatically by the API.\n\nDevices enrolled without a policy are blocked from all functions until a policy\nis applied. **If a policy isn't applied within five minutes, then enrollment\nwill fail and the device will be factory reset.**\n\n### Set a default policy for an enterprise\n\nTo prevent devices from being enrolled without a policy, you can define a single\ndefault policy for an enterprise. To do this, set the `name` of a designated\ndefault policy to `\"default\"`. This policy will then be applied to all newly\nenrolled devices by default, unless another `policyName` is specified in the\ndevice's enrollment token.\n\n### Unspecified values\n\n`_UNSPECIFIED` values are used to represent empty or unset policies. The\nassociated API documentation will outline the default behavior when the policy\nis not explicitly set.\n\nWe generally avoid changing default behavior, except for example when required\nfor security reasons or to align with changes in Android platform. We will\nprovide advance notice to the EMM community when such a change is anticipated to\nallow for EMMs and admins to adapt their policies accordingly.\n\nAs an example, see the `_UNSPECIFIED` enum value for\n[`CrossProfileDataSharing`](https://developers.google.com/android/management/reference/rest/v1/enterprises.policies#crossprofiledatasharing)\n.\n| **Important:** To ensure predictable results and minimize the need for future policy adjustments, we recommend EMMs and admins to explicitly define their policies whenever the required outcome is critical.\n\nUpdate or change a device's policy\n----------------------------------\n\nTo update a policy, call\n[`enterprises.policies.patch`](/android/management/reference/rest/v1/enterprises.policies/patch)\n.\nWhen you update a `policies` resource, the update is enforced on all devices\nassociated with that policy.\n\nTo apply a different policy to the device, call\n[`enterprises.devices.patch`](/android/management/reference/rest/v1/enterprises.devices/patch)\n.\n\n**Note:** We recommend defining one policy per device to enable granular\ndevice-level management capabilities. If there is no need for device-level\ngranularity, AM API supports having a single policy shared across several\ndevices. Automatic patch propagation will occur regardless of your choice to use\nmultiple or a single policy per device."]]
