> For the complete documentation index, see [llms.txt](https://kb.bevica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bevica.com/documentation/guides/integrations-and-connectivity.md).

# Connectivity

Connect Bevica to Microsoft tools and integrations. Set up secure access, connect Excel via Web Services and OData, and use Business Central with Outlook and Teams.

Use this section when you need to connect Bevica to other Microsoft tools, or provide secure access for reporting and integrations.

### Summary

* Set up secure access for external connections to Bevica.
* Connect Excel to live data via Web Services and OData.
* Use Microsoft apps (Outlook and Teams) to work with Bevica without context switching.

### Next steps

* For reporting extracts and live lists in Excel, read [Connecting Excel to Bevica (Web Services & OData)](https://kb.bevica.com/documentation/guides/integrations-and-connectivity/xxxxxxxconnecting_excel_to_bevica_-web_services_and_odata.md).
* To work with contacts and documents from email, set up [Business Central Add-in for Outlook](https://kb.bevica.com/documentation/guides/crm/business_central_add-in_for_outlook_-_features_and_deployment.md).
* To access Bevica from chat and channels, see [Microsoft 365 Teams access to Business Central](https://kb.bevica.com/documentation/guides/crm/microsoft365_teams_access_to_business_central.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://kb.bevica.com/documentation/guides/integrations-and-connectivity.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.
