> For the complete documentation index, see [llms.txt](https://docs.realmjoin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmjoin.com/fr/automatisation/runbooks/runbook-references/org/general/sync-apple-tokens.md).

# Synchroniser les jetons Apple

Synchroniser les jetons d'inscription Apple et VPP avec Intune

### Description

Déclenche une synchronisation des jetons Apple dans Intune, afin que les inscriptions d’appareils depuis Apple Business Manager et les licences d’applications du Volume Purchase Program soient à jour. Un seul type de jeton ou les deux peuvent être synchronisés.

### Emplacement

Organisation → Général → Synchroniser les jetons Apple

**Nom complet du runbook**

rjgit-org\_general\_sync-apple-tokens

### Détails

| Propriété      | Valeur                                                                                   |
| -------------- | ---------------------------------------------------------------------------------------- |
| Version        | 1.0.2                                                                                    |
| Modules requis | <p>RealmJoin.RunbookHelper (>= 0.8.10)<br>Microsoft.Graph.Authentication (>= 2.41.2)</p> |
| Planifiable    | non                                                                                      |

### Autorisations

#### Autorisations d’application

* **Type**: Microsoft Graph
  * DeviceManagementApps.ReadWrite.All
    * *Lit les jetons Apple VPP et déclenche syncLicenses pour chacun d’eux*
  * DeviceManagementServiceConfig.ReadWrite.All
    * *Lit les paramètres d’intégration DEP et déclenche syncWithAppleDeviceEnrollmentProgram pour les jetons ADE*

### Paramètres

#### Type de synchronisation

Synchronisez les jetons du programme d’inscription, les jetons VPP ou les deux.

| Propriété                  | Valeur                |
| -------------------------- | --------------------- |
| Obligatoire                | vrai                  |
| Valeur par défaut          | Les deux              |
| Type                       | Chaîne                |
| Nom d’affichage du portail | Jetons à synchroniser |

**Options du portail**

| Option du portail                                                 | Valeur               |
| ----------------------------------------------------------------- | -------------------- |
| Synchroniser à la fois les jetons d’inscription et les jetons VPP | Les deux             |
| Synchroniser uniquement les jetons du programme d’inscription     | Jetons d’inscription |
| Synchroniser uniquement les jetons VPP                            | Jetons VPP           |

[Retour à l’aperçu de la référence du runbook](/fr/automatisation/runbooks/runbook-references.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.realmjoin.com/fr/automatisation/runbooks/runbook-references/org/general/sync-apple-tokens.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.