ms-graph-types 2.43.1

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,10 @@
+# Microsoft Open Source Code of Conduct
+
+This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
+
+Resources:
+
+- [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/)
+- [Microsoft Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/)
+- Contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with questions or concerns
+- Employees can reach out at [aka.ms/opensource/moderation-support](https://aka.ms/opensource/moderation-support)

package/CONTRIBUTING.md

@@ -0,0 +1,216 @@
+Contribute to this documentation
+
+Thank you for your interest in our documentation!
+
+* [Ways to contribute](#ways-to-contribute)
+* [Contribute using GitHub](#contribute-using-github)
+* [Contribute using Git](#contribute-using-git)
+* [How to use Markdown to format your topic](#how-to-use-markdown-to-format-your-topic)
+* [FAQ](#faq)
+* [More resources](#more-resources)
+
+## Ways to contribute
+
+Here are some ways you can contribute to this documentation:
+
+* To make small changes to an article, [Contribute using GitHub](#contribute-using-github).
+* To make large changes, or changes that involve code, [Contribute using Git](#contribute-using-git).
+* Report documentation bugs via GitHub Issues
+* Request new documentation at the [Office Developer Platform UserVoice](http://officespdev.uservoice.com) site.
+
+## Contribute using GitHub
+
+Use GitHub to contribute to this documentation without having to clone the repo to your desktop. This is the easiest way to create a pull request in this repository. Use this method to make a minor change that doesn't involve code changes. 
+
+**Note** Using this method allows you to contribute to one article at a time.
+
+### To Contribute using GitHub
+
+1. Find the article you want to contribute to on GitHub. 
+
+    If the article is in MSDN, choose the **suggest and submit changes** link in the **Contribute to this content** section and you'll be taken to the same article on GitHub.
+2. Once you are on the article in GitHub, sign in to GitHub (get a free account [Join GitHub](https://github.com/join).
+3. Choose the **pencil icon** (edit the file in your fork of this project) and make your changes in the **<>Edit file** window. 
+4. Scroll to the bottom and enter a description.
+5. Choose **Propose file change**>**Create pull request**.
+
+You now have successfully submitted a pull request. Pull requests are typically reviewed within 10 business days. 
+
+
+## Contribute using Git
+
+Use Git to contribute substantive changes, such as:
+
+* Contributing code.
+* Contributing changes that affect meaning.
+* Contributing large changes to text.
+* Adding new topics.
+
+### To Contribute using Git
+
+1. If you don't have a GitHub account, set one up at [GitHub](https://github.com/join). 
+2. After you have an account, install Git on your computer. Follow the steps in [Setting up Git Tutorial](https://help.github.com/articles/set-up-git/).
+3. To submit a pull request using Git, follow the steps in [Use GitHub, Git, and this repository](#use-github-git-and-this-repository).
+4. You will be asked to sign the Contributor's License Agreement if you are:
+
+    * A member of the Microsoft Open Technologies group.
+    * A contributors who doesn't work for Microsoft.
+
+As a community member, you must sign the Contribution License Agreement (CLA) before you can contribute large submissions to a project. You only need to complete and submit the documentation once. Carefully review the document. You may be required to have your employer sign the document.
+
+Signing the CLA does not grant you rights to commit to the main repository, but it does mean that the Office Developer and Office Developer Content Publishing teams will be able to review and approve your contributions. You will be credited for your submissions.
+
+Pull requests are typically reviewed within 10 business days.
+
+## Use GitHub, Git, and this repository
+
+**Note:** Most of the information in this section can be found in [GitHub Help] articles.  If you're familiar with Git and GitHub, skip to the **Contribute and edit content** section for the specifics of the code/content flow of this repository.
+
+### To set up your fork of the repository
+
+1.	Set up a GitHub account so you can contribute to this project. If you haven't done this, go to [GitHub](https://github.com/join) and do it now.
+2.	Install Git on your computer. Follow the steps in the [Setting up Git Tutorial] [Set Up Git].
+3.	Create your own fork of this repository. To do this, at the top of the page,  choose the **Fork** button.
+4.	Copy your fork to your computer. To do this, open Git Bash. At the command prompt enter:
+
+        git clone https://github.com/<your user name>/<repo name>.git
+
+    Next, create a reference to the root repository by entering these commands:
+
+        cd <repo name>
+        git remote add upstream https://github.com/microsoftgraph/<repo name>.git
+        git fetch upstream
+
+Congratulations! You've now set up your repository. You won't need to repeat these steps again.
+
+### Contribute and edit content
+
+To make the contribution process as seamless as possible, follow these steps.
+
+#### To contribute and edit content
+
+1. Create a new branch.
+2. Add new content or edit existing content.
+3. Submit a pull request to the main repository.
+4. Delete the branch.
+
+**Important** Limit each branch to a single concept/article to streamline the work flow and reduce the chance of merge conflicts. Content appropriate for a new branch includes:
+
+* A new article.
+* Spelling and grammar edits.
+* Applying a single formatting change across a large set of articles (for example, applying a new copyright footer).
+
+#### To create a new branch
+
+1.	Open Git Bash.
+2.	At the Git Bash command prompt, type `git pull upstream master:<new branch name>`. This creates a new branch locally that is copied from the latest MicrosoftGraph master branch.
+3.	At the Git Bash command prompt, type `git push origin <new branch name>`. This alerts GitHub to the new branch. You should now see the new branch in your fork of the repository on GitHub.
+4.	At the Git Bash command prompt, type `git checkout <new branch name>` to switch to your new branch.
+
+#### Add new content or edit existing content
+
+You navigate to the repository on your computer by using File Explorer. The repository files are in `C:\Users\<yourusername>\<repo name>`.
+
+To edit files, open them in an editor of your choice and modify them. To create a new file, use the editor of your choice and save the new file in the appropriate location in your local copy of the repository. While working, save your work frequently.
+
+The files in `C:\Users\<yourusername>\<repo name>` are a working copy of the new branch that you created in your local repository. Changing anything in this folder doesn't affect the local repository until you commit a change. To commit a change to the local repository, type the following commands in GitBash:
+
+    git add .
+    git commit -v -a -m "<Describe the changes made in this commit>"
+
+The `add` command adds your changes to a staging area in preparation for committing them to the repository. The period after the `add` command specifies that you want to stage all of the files that you added or modified, checking subfolders recursively. (If you don't want to commit all of the changes, you can add specific files. You can also undo a commit. For help, type `git add -help` or `git status`.)
+
+The `commit` command applies the staged changes to the repository. The switch `-m` means you are providing the commit comment in the command line. The -v and -a switches can be omitted. The -v switch is for verbose output from the command, and -a does what you already did with the add command.
+
+You can commit multiple times while you are doing your work, or you can commit once when you're done.
+
+#### Submit a pull request to the main repository
+
+When you're finished with your work and are ready to have it merged into the main repository, follow these steps.
+
+#### To submit a pull request to the main repository
+
+1.	In the Git Bash command prompt, type `git push origin <new branch name>`. In your local repository, `origin` refers to your GitHub repository that you cloned the local repository from. This command pushes the current state of your new branch, including all commits made in the previous steps, to your GitHub fork.
+2.	On the GitHub site, navigate in your fork to the new branch.
+3.	Choose the **Pull Request** button at the top of the page.
+4.	Verify the Base branch is `microsoftgraph/<repo name>@master` and the Head branch is `<your username>/<repo name>@<branch name>`.
+5.	Choose the **Update Commit Range** button.
+6.	Add a title to your pull request, and describe all the changes you're making.
+7.	Submit the pull request.
+
+One of the site administrators will process your pull request. Your pull request will surface on the microsoftgraph/<repo name> site under Issues. When the pull request is accepted, the issue will be resolved.
+
+#### Create a new branch after merge
+
+After a branch is successfully merged (that is, your pull request is accepted), don't continue working in that local branch. This can lead to merge conflicts if you submit another pull request. To do another update, create a new local branch from the successfully merged upstream branch, and then delete your initial local branch.
+
+For example, if your local branch X was successfully merged into the OfficeDev/microsoft-graph-docs master branch and you want to make additional updates to the content that was merged. Create a new local branch, X2, from the OfficeDev/microsoft-graph-docs master branch. To do this, open GitBash and execute the following commands:
+
+    cd microsoft-graph-docs
+    git pull upstream master:X2
+    git push origin X2
+
+You now have local copies (in a new local branch) of the work that you submitted in branch X. The X2 branch also contains all the work other writers have merged, so if your work depends on others' work (for example, shared images), it is available in the new branch. You can verify that your previous work (and others' work) is in the branch by checking out the new branch...
+
+    git checkout X2
+
+...and verifying the content. (The `checkout` command updates the files in `C:\Users\<yourusername>\microsoft-graph-docs` to the current state of the X2 branch.) Once you check out the new branch, you can make updates to the content and commit them as usual. However, to avoid working in the merged branch (X) by mistake, it's best to delete it (see the following **Delete a branch** section).
+
+#### Delete a branch
+
+Once your changes are successfully merged into the main repository, delete the branch you used because you no longer need it.  Any additional work should be done in a new branch.  
+
+#### To delete a branch
+
+1.	In the Git Bash command prompt, type `git checkout master`. This ensures that you aren't in the branch to be deleted (which isn't allowed).
+2.	Next, at the command prompt, type `git branch -d <branch name>`. This deletes the branch on your computer only if it has been successfully merged to the upstream repository. (You can override this behavior with the `–D` flag, but first be sure you want to do this.)
+3.	Finally, type `git push origin :<branch name>` at the command prompt (a space before the colon and no space after it).  This will delete the branch on your github fork.  
+
+Congratulations, you have successfully contributed to the project!
+
+## How to use Markdown to format your topic
+
+### Article template
+
+The [markdown template](/articles/0-markdown-template-for-new-articles.md) contains the basic Markdown for a topic that includes a table of contents, sections with subheadings, links to other Office developer topics, links to other sites, bold text, italic text, numbered and bulleted lists, code snippets, and images. 
+
+
+### Standard Markdown
+
+All of the articles in this repository use Markdown. A complete introduction (and listing of all the syntax) can be found at [Markdown Home] [].
+ 
+## FAQ
+
+### How do I get a GitHub account?
+
+Fill out the form at [Join GitHub](https://github.com/join) to open a free GitHub account. 
+
+### Where do I get a Contributor's License Agreement? 
+
+You will automatically be sent a notice that you need to sign the Contributor's License Agreement (CLA) if your pull request requires one. 
+
+As a community member, **you must sign the Contribution License Agreement (CLA) before you can contribute large submissions to this project**. You only need complete and submit the documentation once. Carefully review the document. You may be required to have your employer sign the document.
+
+### What happens with my contributions?
+
+When you submit your changes, via a pull request, our team will be notified and will review your pull request. You will receive notifications about your pull request from GitHub; you may also be notified by someone from our team if we need more information. We reserve the right to edit your submission for legal, style, clarity, or other issues.
+ 
+### Can I become an approver for this repository's GitHub pull requests?
+
+Currently, we are not allowing external contributors to approve pull requests in this repository.
+
+### How soon will I get a response about my change request or issue?
+
+We typically review pull requests and respond to issues within 10 business days.
+
+## More resources
+
+* To learn more about Markdown, go to the Git creator's site [Daring Fireball].
+* To learn more about using Git and GitHub, first check out the [GitHub Help section] [GitHub Help].
+
+[GitHub Home]: http://github.com
+[GitHub Help]: http://help.github.com/
+[Set Up Git]: http://help.github.com/win-set-up-git/
+[Markdown Home]: http://daringfireball.net/projects/markdown/
+[Daring Fireball]: http://daringfireball.net/
+

package/LICENSE

@@ -0,0 +1,25 @@
+Microsoft Graph TypeScript Typings
+
+Copyright 2015 Microsoft Corporation
+
+All right reserved.
+
+MIT License
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

package/README-Localized/README-es-es.md

@@ -0,0 +1,152 @@
+[![identificador de versión npm](https://img.shields.io/npm/v/@microsoft/microsoft-graph-types.svg)](https://www.npmjs.com/package/@microsoft/microsoft-graph-types)
+
+# Tipos de TypeScript de Microsoft Graph
+Las definiciones de TypeScript de Microsoft Graph permiten a los editores ofrecer IntelliSense en objetos de Microsoft Graph, como usuarios, mensajes y grupos.
+
+## Instalación
+
+Se recomienda incluir el archivo .d.ts al descargar este paquete a través de [npm](https://www.npmjs.com/).
+
+```bash
+
+# Install types and save in package.json as a development dependency
+npm install @microsoft/microsoft-graph-types --save-dev
+
+```
+
+
+![GIF que muestra IntelliSense y finalización automática para entidades de Microsoft Graph en Visual Studio Code ](https://github.com/microsoftgraph/msgraph-typescript-typings/raw/master/typings-demo.gif)
+## Ejemplos
+En los ejemplos siguientes se presupone que el usuario tiene un token de acceso válido. Hemos usado [isomorphic-fetch](https://www.npmjs.com/package/isomorphic-fetch) para realizar solicitudes, pero también puede usar [nuestra biblioteca cliente de JavaScript](https://github.com/microsoftgraph/msgraph-sdk-javascript) u otras bibliotecas.
+```typescript
+import * as MicrosoftGraph from "@microsoft/microsoft-graph-types"
+
+import * from 'isomorphic-fetch';
+const accessToken:string = "";
+```
+### Mostrar mis mensajes recientes
+```typescript
+let url = "https://graph.microsoft.com/v1.0/me/messages";
+let request = new Request(url, {
+    method: "GET",
+    headers: new Headers({
+        "Authorization": "Bearer " + accessToken
+    })
+});
+
+fetch(request)
+.then((response) => {
+    response.json().then((res) => {
+        let messages:[MicrosoftGraph.Message] = res.value;
+        for (let msg of messages) { //iterate through the recent messages
+            console.log(msg.subject);
+            console.log(msg.toRecipients[0].emailAddress.address);
+        }
+    });
+
+})
+.catch((error) => {
+    console.error(error);
+});
+```
+### Enviar un correo electrónico como el usuario conectado
+```typescript
+// Create the message object
+
+// Note that all the properties must follow the interface definitions.
+// For example, this will not compile if you try to type "xml" instead of "html" for contentType. 
+
+let mail:MicrosoftGraph.Message = {
+    subject: "Microsoft Graph TypeScript Sample",
+    toRecipients: [{
+        emailAddress: {
+            address: "microsoftgraph@example.com"
+        }
+    }],
+    body: {
+        content: "<h1>Microsoft Graph TypeScript Sample</h1>Try modifying the sample",
+        contentType: "html"
+    }
+}
+// send the email by sending a POST request to the Microsoft Graph
+let url = "https://graph.microsoft.com/v1.0/users/me/sendMail";
+let request = new Request(
+            url, {
+                method: "POST",
+                body: JSON.stringify({
+                    message: mail
+                }),
+                headers: new Headers({
+                    "Authorization": "Bearer " + accessToken,
+                    'Content-Type': 'application/json'
+                })
+            }
+        );
+        
+fetch(request)
+.then((response) => {
+    if(response.ok === true) {
+        console.log("Mail sent successfully..!!");
+    }
+})
+.catch((err) => {
+    console.error(err);
+});
+
+```
+## Soporte de Microsoft Graph beta
+Si desea probar los puntos de conexión de la versión beta de Microsoft Graph, puede usar esos tipos simultáneamente con los tipos v1.0.
+
+Actualice el archivo package.json con lo siguiente:
+
+```javascript
+  "devDependencies": {
+    // import published v1.0 types with a version from NPM
+    "@microsoft/microsoft-graph-types": "^0.4.0",
+
+    // import beta types from the beta branch on the GitHub repo
+    "@microsoft/microsoft-graph-types-beta": "microsoftgraph/msgraph-typescript-typings#beta"
+  }
+}
+```
+
+Import the beta types from `@microsoft/microsoft-graph-types-beta`
+```typescript
+// import individual entities
+import {User as BetaUser} from "@microsoft/microsoft-graph-types-beta"
+
+// or import everything under MicrosoftGraphBeta
+import * as MicrosoftGraphBeta from "@microsoft/microsoft-graph-types-beta"
+```
+
+## Editores admitidos
+Cualquier proyecto TypeScript puede usar estos tipos al usar al menos TypeScript 2.0 Hemos probado a incluir los tipos como dependencia en los siguientes editores.
+* Visual Studio Code
+* WebStorm
+* Atom with the [atom-typescript](https://atom.io/packages/atom-typescript) plugin
+
+## Preguntas y comentarios
+
+Nos encantaría recibir sus comentarios sobre el proyecto de definiciones de TypeScript. Puede enviarnos sus preguntas y sugerencias a través de la sección [Problemas](https://github.com/microsoftgraph/msgraph-typescript-typings/issues) de este repositorio.
+
+
+## Colaboradores
+Vea la [directrices de contribución](CONTRIBUTING.md).
+
+## Recursos adicionales
+
+* [Microsoft Graph](https://graph.microsoft.io)
+* [Centro para desarrolladores de Office](http://dev.office.com/)
+* [Biblioteca cliente de JavaScript de Microsoft Graph](https://github.com/microsoftgraph/msgraph-sdk-javascript)
+
+## Informes de seguridad
+
+Si encuentra un problema de seguridad con nuestras bibliotecas o servicios, informe a [secure@microsoft.com](mailto:secure@microsoft.com) con todos los detalles posibles. Es posible que el envío pueda optar a una recompensa a través del programa [Microsoft Bounty](http://aka.ms/bugbounty). No publique problemas de seguridad en problemas de GitHub ni ningún otro sitio público. Nos pondremos en contacto con usted rápidamente tras recibir la información. Le animamos a que obtenga notificaciones de los incidentes de seguridad que se produzcan; para ello, visite [esta página](https://technet.microsoft.com/en-us/security/dd252948) y suscríbase a las alertas de avisos de seguridad.
+
+## Licencia
+
+Copyright (c) Microsoft Corporation. Todos los derechos reservados. Publicado bajo la licencia MIT (la "Licencia").
+
+## Valoramos y nos adherimos al Código de conducta de código abierto de Microsoft
+
+Este proyecto ha adoptado el [Código de conducta de código abierto de Microsoft](https://opensource.microsoft.com/codeofconduct/). Para obtener más información, vea [Preguntas frecuentes sobre el código de conducta](https://opensource.microsoft.com/codeofconduct/faq/) o póngase en contacto con [opencode@microsoft.com](mailto:opencode@microsoft.com) si tiene otras preguntas o comentarios.

package/README-Localized/README-fr-fr.md

@@ -0,0 +1,152 @@
+[![Badge de version npm](https://img.shields.io/npm/v/@microsoft/microsoft-graph-types.svg)](https://www.npmjs.com/package/@microsoft/microsoft-graph-types)
+
+# Types TypeScript Microsoft Graph
+Les définitions TypeScript Microsoft Graph permettent aux éditeurs de fournir des fonctionnalités IntelliSense sur les objets Microsoft Graph, notamment les utilisateurs, les messages et les groupes.
+
+## Installation
+
+Nous vous recommandons d’inclure le fichier .d.ts en téléchargeant ce package via [npm](https://www.npmjs.com/).
+
+```bash
+
+# Install types and save in package.json as a development dependency
+npm install @microsoft/microsoft-graph-types --save-dev
+
+```
+
+
+![Image GIF montrant IntelliSense et la saisie semi-automatique des entités Microsoft Graph dans Visual Studio Code](https://github.com/microsoftgraph/msgraph-typescript-typings/raw/master/typings-demo.gif)
+## Exemples
+Les exemples suivants partent du principe que vous possédez un jeton d’accès valide. Nous avons utilisé [isomorphic-FETCH](https://www.npmjs.com/package/isomorphic-fetch) pour effectuer des requêtes, mais vous pouvez utiliser [notre bibliothèque cliente JavaScript](https://github.com/microsoftgraph/msgraph-sdk-javascript) ou d’autres bibliothèques également.
+```typescript
+import * as MicrosoftGraph from "@microsoft/microsoft-graph-types"
+
+import * from 'isomorphic-fetch';
+const accessToken:string = "";
+```
+### Répertorier mes messages récents
+```typescript
+let url = "https://graph.microsoft.com/v1.0/me/messages";
+let request = new Request(url, {
+    method: "GET",
+    headers: new Headers({
+        "Authorization": "Bearer " + accessToken
+    })
+});
+
+fetch(request)
+.then((response) => {
+    response.json().then((res) => {
+        let messages:[MicrosoftGraph.Message] = res.value;
+        for (let msg of messages) { //iterate through the recent messages
+            console.log(msg.subject);
+            console.log(msg.toRecipients[0].emailAddress.address);
+        }
+    });
+
+})
+.catch((error) => {
+    console.error(error);
+});
+```
+### Envoyer un e-mail en tant qu’utilisateur connecté
+```typescript
+// Create the message object
+
+// Note that all the properties must follow the interface definitions.
+// For example, this will not compile if you try to type "xml" instead of "html" for contentType. 
+
+let mail:MicrosoftGraph.Message = {
+    subject: "Microsoft Graph TypeScript Sample",
+    toRecipients: [{
+        emailAddress: {
+            address: "microsoftgraph@example.com"
+        }
+    }],
+    body: {
+        content: "<h1>Microsoft Graph TypeScript Sample</h1>Try modifying the sample",
+        contentType: "html"
+    }
+}
+// send the email by sending a POST request to the Microsoft Graph
+let url = "https://graph.microsoft.com/v1.0/users/me/sendMail";
+let request = new Request(
+            url, {
+                method: "POST",
+                body: JSON.stringify({
+                    message: mail
+                }),
+                headers: new Headers({
+                    "Authorization": "Bearer " + accessToken,
+                    'Content-Type': 'application/json'
+                })
+            }
+        );
+        
+fetch(request)
+.then((response) => {
+    if(response.ok === true) {
+        console.log("Mail sent successfully..!!");
+    }
+})
+.catch((err) => {
+    console.error(err);
+});
+
+```
+## Prise en charge de Microsoft Graph bêta
+Si vous voulez tester les points de terminaison Microsoft Graph bêta, vous pouvez utiliser ces types simultanément avec les types v 1.0.
+
+Mettez à jour votre fichier package.json avec ce qui suit :
+
+```javascript
+  "devDependencies": {
+    // import published v1.0 types with a version from NPM
+    "@microsoft/microsoft-graph-types": "^0.4.0",
+
+    // import beta types from the beta branch on the GitHub repo
+    "@microsoft/microsoft-graph-types-beta": "microsoftgraph/msgraph-typescript-typings#beta"
+  }
+}
+```
+
+Importez des types bêta de `@microsoft/microsoft-graph-types-beta`
+```typescript
+// import individual entities
+import {User as BetaUser} from "@microsoft/microsoft-graph-types-beta"
+
+// or import everything under MicrosoftGraphBeta
+import * as MicrosoftGraphBeta from "@microsoft/microsoft-graph-types-beta"
+```
+
+## Éditeurs pris en charge
+Tout projet TypeScript peut utiliser ces types avec au moins TypeScript 2.0. Nous avons testé l’inclusion des types en tant que dépendances dans les éditeurs suivants.
+* Visual Studio Code
+* WebStorm
+* Atom avec le plug-in [atom-typescript](https://atom.io/packages/atom-typescript)
+
+## Questions et commentaires
+
+Nous serions ravis de connaître votre opinion sur le projet de définitions TypeScript. Vous pouvez nous faire part de vos questions et suggestions dans la rubrique [Problèmes](https://github.com/microsoftgraph/msgraph-typescript-typings/issues) de ce référentiel.
+
+
+## Contribution
+Reportez-vous aux [instructions sur la contribution](CONTRIBUTING.md).
+
+## Ressources supplémentaires
+
+* [Microsoft Graph](https://graph.microsoft.io)
+* [Centre des développeurs Office](http://dev.office.com/)
+* [Bibliothèque cliente JavaScript Microsoft Graph](https://github.com/microsoftgraph/msgraph-sdk-javascript)
+
+## Génération de rapports de sécurité
+
+Si vous rencontrez un problème de sécurité avec nos bibliothèques ou services, signalez-le à l’adresse [secure@microsoft.com](mailto:secure@microsoft.com) avec autant de détails que possible. Votre envoi vous donnera sans doute droit à une prime via le programme [Bounty de Microsoft](http://aka.ms/bugbounty). Merci de ne pas publier de problèmes de sécurité sur le site des problèmes GitHub ou sur un autre site public. Nous vous contacterons rapidement dès réception des informations. Nous vous encourageons à activer les notifications d’incidents de sécurité en vous rendant sur [cette page](https://technet.microsoft.com/en-us/security/dd252948) et en vous abonnant aux alertes d’avis de sécurité.
+
+## Licence
+
+Copyright (c) Microsoft Corporation. Tous droits réservés. Soumis à la licence MIT (la "Licence") ;
+
+## Nous respectons le code de conduite Open Source de Microsoft.
+
+Ce projet a adopté le [code de conduite Open Source de Microsoft](https://opensource.microsoft.com/codeofconduct/). Pour en savoir plus, reportez-vous à la [FAQ relative au code de conduite](https://opensource.microsoft.com/codeofconduct/faq/) ou contactez [opencode@microsoft.com](mailto:opencode@microsoft.com) pour toute question ou tout commentaire.