> For the complete documentation index, see [llms.txt](https://docs.hivel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hivel.ai/integrations/scm/azure/azure-git-server.md).
# Azure GIT Server
#### Data Access by Hivel
* Hivel accesses the past 60-90 days of commits and pull requests from active repositories during the initial sync.
#### Whitelist Necessary IP Addresses
For a secure and uninterrupted connection, make sure to whitelist the following IP addresses:
* **Mandatory IPs**:
* 107.23.139.76
* 3.219.89.23
* **Recommended, but Optional IPs**:
* 45.119.114.218
* 183.82.116.218
#### Authorization Mechanism
* Hivel gets access using a Personal Access Token, which can be created using this [link](https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops\&tabs=Windows#create-a-pat).
* Users maintain full control and can withdraw access anytime by revoking the Personal Access Token.
* Ensure '**All accessible organizations'** is selected while creating the Personal Access Token.\
\
\
\
**Requirements**
* Ensure to create the Personal Access Token from an account that has "Project Administrator" permissions for all relevant projects and repositories.
**Best Practice**
* Opt for a service account rather than an individual-linked account.
* Service accounts are typically overseen by the company's admin.
**Personal Access Token Permissions**
* Please ensure you select all the options below while creating a Personal Access Token.
* **Project And Team**: Read
* **User Profile**: Read
* **Code**: Read
* **Build**: Read
* **Graph:** Read
* **Work Items:** Read \
\
\
\
\
\
**You are almost done.**
* Once a Personal Access Token is created, please copy it and share it with the Hivel team.
* You will receive an email from the Hivel team once your data is all up and running.