> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/create-a-microsoft-l2tp-vpn-entry.md).

# Create a Microsoft L2TP VPN entry

Create a Microsoft L2TP VPN entry in Remote Desktop Manager with a pre-shared key and the correct authentication method.

You can create a Microsoft L2TP VPN entry in Remote Desktop Manager.

1. First you will need to create a new ***VPN Microsoft*** entry with the basic information and settings.
2. In the ***General - Connection*** section, use the drop down menu next to the ***VPN type***, and select ***L2TP*** instead of ***Automatic***.
3. Enter your ***Pre-shared key*** provided from Microsoft.
4. Fill in the information for the ***Username***, ***Domain***, and ***Password***.
5. Optional: The ***Auth method*** can be different for each user (it is by default set to ***PAP***), depending on your Microsoft VPN configuration. Use the drop down menu to change it.

   | Option     | Description                                 |
   | ---------- | ------------------------------------------- |
   | PAP        | Unencrypted password                        |
   | CHAP       | Challenge Handshake Authentication Protocol |
   | MS-CHAP v2 | Microsoft CHAP Version 2                    |
   | EAP        | Extensible Authentication Protocol          |
6. Click ***OK*** to save.


---

# 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.devolutions.net/rdm/knowledge-base/how-to-articles/create-a-microsoft-l2tp-vpn-entry.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.