Microsoft 365 Copilot Connector: Overview

You can unlock new possibilities for your organization with Microsoft 365 Copilot Connectors. These connectors link Microsoft Copilot to external data sources, moving information into Microsoft Graph for powerful semantic indexing. This connection gives you a unified view of your data and makes knowledge discovery much easier. IT professionals often use Copilot Connectors for tasks like managing technical guides or tracking assets, which saves time and improves accuracy.

Key Takeaways

• Copilot Connectors link Microsoft Copilot to various data sources, enhancing data access and knowledge discovery.
• Two main types of connectors exist: Synced Connectors for indexed data and Federated Connectors for real-time access.
• Using Copilot Connectors improves productivity by streamlining tasks and reducing time spent on routine activities.
• Unified search capabilities allow users to find information across multiple platforms from a single search box.
• Customization options enable organizations to tailor Copilot to their specific needs using low-code and pro-code tools.
• Strong data governance is essential to protect sensitive information and ensure compliance with regulations.
• Regular training and support help teams effectively adopt and utilize Copilot Connectors for better outcomes.
• Planning and monitoring connector usage can optimize performance and enhance security across your organization.

9 Surprising Facts About Microsoft Copilot Connectors

• They connect more than just Microsoft services — microsoft copilot connectors can integrate third-party apps and legacy systems without extensive custom code.
• Connectors enable natural language access to data sources, letting Copilot query databases, CRMs, and file systems using plain English prompts.
• Many connectors support real-time data flows, so Copilot can act on up-to-date information rather than only static snapshots.
• Security is built-in: connectors can leverage enterprise identity and conditional access policies to enforce least-privilege access automatically.
• Custom connectors let organizations surface proprietary APIs and internal tools to Copilot in hours, not months.
• Metadata-driven mapping simplifies schema differences — Copilot Connectors can reconcile disparate data models behind the scenes.
• They support event-driven automation, allowing Copilot to trigger workflows or notifications when specific conditions are met in connected systems.
• Governance controls let admins whitelist or blacklist connectors, track usage, and audit data access from a central portal.
• Performance optimizations like caching and query folding are commonly used, so even complex queries through microsoft copilot connectors can remain fast and scalable.

Copilot Connectors Overview

Definition and Purpose

You can think of Copilot Connectors as the bridge that links Microsoft Copilot to many different data sources inside and outside your organization. These connectors enrich Copilot with data from enterprise systems like ERP and CRM, giving you access to comprehensive insights and seamless integration within your existing tools. When you use Copilot Connectors, you make it possible for Copilot to summarize and analyze information from multiple sources. This helps you find answers faster and work more efficiently.

Note: Microsoft 365 Copilot Connectors are designed to bring together data from many places, so you can use Microsoft Search and other tools to discover knowledge across your organization.

The main purposes of Copilot Connectors include:

Connector Types

You will find two main types of connectors in the Microsoft 365 Copilot Connectors Gallery. Each type serves a different purpose and fits different data needs.

Synced Connectors

Synced connectors index data directly into Microsoft Graph. This means your organization can access and search this data through Microsoft 365 applications. If you want to make sure everyone in your company can find important documents or records, synced connectors are the right choice. They work well for large collections of files and can handle millions of documents, making them scalable for big organizations.

Federated Connectors

Federated connectors fetch content live from the original data source without storing or indexing it in Microsoft Graph. You use federated connectors when you need real-time access to information that changes often or when you do not want to move data from its original location. This type of connector is helpful for situations where data privacy or compliance rules require you to keep information in its source system.

Core Components

When you set up Copilot Connectors, you use several core components that work together to connect your data sources to Copilot. These components include:

• Connectors from Microsoft Power Platform, which act as wrappers around APIs. They let Copilot Studio communicate with other apps and services.
• Prebuilt connectors, which give you built-in connections to popular services.
• Standard connectors, included with all Copilot Studio plans.
• Premium connectors, available in select plans for advanced needs.
• Custom connectors, which allow you to connect to any public API if you have unique requirements.

You can also extend Copilot Studio’s abilities by using topics, tools, knowledge sources, and even other agents. These features help you integrate data from many enterprise systems and APIs, so Copilot can access and use this information effectively.

Tip: The Microsoft 365 Copilot Connectors Gallery makes it easy for you to discover, manage, and deploy the connectors that best fit your organization’s needs.

With Copilot Connectors, you can unify knowledge across departments, empower distributed teams, and ensure continuous compliance with security and privacy standards. This approach helps you break down data silos and gives everyone in your organization the information they need to succeed.

Copilot Connectors Integration

Microsoft Graph Connection

Data Flow

When you use Copilot Connectors, your data moves securely into Microsoft Graph. Microsoft Graph acts as the main hub for your organization’s information. You can connect different data sources using the Microsoft Graph connectors SDK. This SDK lets you build custom connectors that bring in data from many systems. Once you set up a connector, it ingests and indexes your content. This process makes your data searchable and ready for Copilot to use in Microsoft 365 apps.

To manage these connectors, you need access to the Microsoft 365 Admin Center. You should have Global Administrator or Search Administrator permissions. Each connector has its own data indexing limits, so you need to monitor usage, especially in large organizations. Your Microsoft 365 tenant must also support semantic indexing. This feature helps Copilot deliver context-aware search results.

Permissions

Security is a top priority when you connect external data. Microsoft Entra ID manages authentication and permissions for Copilot Connectors. Before you build a custom connector, you must register an application. You then grant admin consent for the required Microsoft Graph permissions in the Microsoft Entra admin center. This process ensures only authorized users and apps can access your organization’s data.

Tip: Always review permissions before connecting new data sources. This step helps protect sensitive information and keeps your environment secure.

External Platform Access

Copilot Connectors let you reach data from popular platforms like Salesforce and ServiceNow. For Salesforce, you set up a Connected App and register an OAuth application. Your account needs API access permissions. For ServiceNow, you create a service account with roles for incidents, problems, changes, and knowledge base access. You also configure OAuth 2.0 authentication. These steps allow Copilot to pull in real-time data from these platforms. You can also connect to custom databases and other business systems, making your Microsoft 365 environment even more powerful.

Many organizations use Copilot Connectors to save time and reduce manual work. You can focus on higher-value tasks while Copilot handles data gathering and analysis. This integration helps teams across departments work more efficiently.

Contextual AI Responses

Copilot Connectors do more than just move data—they help Copilot deliver smarter answers. Microsoft 365 Copilot uses a process called Retrieval-Augmented Generation (RAG). First, Copilot retrieves context from your Microsoft 365 environment. It then embeds and ranks the content, injects it into the prompt for the language model, and generates an answer using your actual data. Copilot also applies business logic and safety checks to make sure the response is accurate.

For example, if you ask Copilot in Excel for a Q4 revenue trend summary, it gathers data from Excel, SharePoint, Teams, and even Outlook. Instead of a generic answer, you get a tailored analysis with charts and tables based on your organization’s real numbers. This approach ensures every response is relevant and grounded in your own data.

Copilot Connectors Benefits

Unified Search

You can transform your organization’s search experience with unified search. Copilot Connectors bring together data from many sources, making it easier for you to find what you need. When you use these connectors, you do not have to search each system separately. Instead, you get a single search box that covers all your connected platforms.

• You can access data from Salesforce, ServiceNow, Google Drive, and more, all within Microsoft 365.
• Over 100 connectors help you summarize and analyze information from different datasets.
• Search results from external sources appear alongside your Microsoft 365 files in SharePoint.
• You see a unified view of people and content, even when the data comes from different systems.
• Security trimming ensures you only see information you have permission to access.

This unified approach helps you discover knowledge faster and reduces the time you spend switching between tools.

Productivity Boost

You can boost your productivity by using Copilot Connectors. Studies show that users complete tasks much faster and with less effort when they use Copilot in Microsoft 365. The following table highlights some key findings:

You can see that Copilot Connectors help you work smarter. You spend less time on routine tasks and more time on important projects. Your emails become clearer, your meetings get summarized quickly, and your team can solve problems faster.

Customization Options

You have many ways to customize your Copilot experience. Copilot Connectors let you connect to the data sources that matter most to your business. You can use low-code tools like Copilot Studio or Microsoft 365 Copilot to set up connections easily. If you need more advanced options, you can use pro-code tools such as Visual Studio Code or Teams SDK.

You can also add plugins to give Copilot new abilities or connect to unique data through Microsoft Graph Connectors. This flexibility means you can tailor Copilot to fit your exact needs, whether you want to analyze sales data, manage customer support, or access custom databases.

Tip: Customization helps you get the most value from your Microsoft 365 investment. You can adapt Copilot to support your team’s workflows and business goals.

Data Governance

You need strong data governance to protect your organization’s information and meet regulatory requirements. Copilot Connectors help you manage your data with built-in features that support security, compliance, and control. When you connect external data sources, you want to make sure only the right people can access sensitive information. Good data governance gives you peace of mind and helps your business avoid risks.

Copilot Connectors use several tools to keep your data safe and compliant. You can see these features and their benefits in the table below:

You can use validation to set clear boundaries for your data. This means you decide who can see or use certain information. If someone tries to access data they should not see, the system blocks them. This step helps you protect confidential files and customer records.

Continuous monitoring gives you real-time oversight. You can track how Copilot interacts with your data sources. If you notice unusual activity, you can respond quickly. This feature helps you spot problems before they become bigger issues. It also supports your compliance team by showing that you follow your organization’s data policies.

Administrative controls let you review permissions and security settings on a regular schedule. You can check which users or apps have access to each data source. If you find extra permissions that are not needed, you can remove them. This practice keeps your environment secure and prevents “permission creep,” where users slowly gain more access than they need.

Tip: Regular reviews and monitoring help you stay ahead of compliance audits and reduce the risk of data breaches.

With Copilot Connectors, you can unify your data while keeping control over who can access it. You support your compliance goals and build trust with customers and partners. Strong data governance also makes it easier to adapt to new regulations as they appear. You can focus on using your data to drive business results, knowing that your information stays protected.

Limitations and Considerations

Security Challenges

When you connect different data sources to Microsoft 365 Copilot, you must think about security. Each new connection can introduce risks if not managed carefully. You want to make sure only trusted sources feed information into your system. Attackers may try to use custom actions or apps to gain access to sensitive data. You also need to control who can use integrated apps and what those apps can do.

Here is a table that shows common security challenges and how you can address them:

Tip: Always review your security settings when you add new connectors. Regular checks help you keep your environment safe.

Privacy Concerns

Protecting privacy is just as important as securing your data. You need to make sure that only the right people can see sensitive information. Sometimes, users may have too much access, or data may not be labeled correctly. You also want to prevent prompt injection attacks, where someone tries to trick the system with harmful input.

The table below highlights key privacy concerns and best practices to help you manage them:

Note: Good privacy practices help you build trust with your users and meet compliance requirements.

Integration Complexity

Connecting Copilot to many systems can be complex. You may face challenges with large data schemas, technical setup, or slow response times from older systems. Sometimes, you need special knowledge to configure secure connections, especially with platforms like SAP or Dynamics. You might also see delays when indexing new files or extracting data from complex documents.

Here are some ways you can simplify integration:

• Use prebuilt connectors to reduce setup time and technical barriers.
• Build custom connectors for unique business needs.
• Learn about your data types, expected latency, and authentication requirements before you start.
• Plan for possible delays when indexing large files or working with legacy systems.
• Review permissions for service principals and make sure they match your security policies.

By understanding these complexities, you can plan your integration more effectively and avoid common pitfalls.

Licensing Factors

You need to understand licensing before you deploy Microsoft 365 Copilot Connectors. Licensing determines which features you can use and how you can scale your solution. Microsoft offers different plans and add-ons, so you should review your options carefully.

You start with a Microsoft 365 subscription. Not all plans include Copilot or Copilot Connectors. You may need to purchase Microsoft 365 Copilot as an add-on. Some advanced connectors or premium features require extra licenses. You should check the Microsoft 365 Copilot Connectors Gallery for the latest list of available connectors and their licensing requirements.

Here is a table to help you compare common licensing options:

You should also consider how many users need access. Some licenses are per user, while others are per tenant. If your organization has many departments or remote teams, you may need to plan for extra seats. You can assign licenses through the Microsoft 365 Admin Center. This tool helps you manage who gets access to Copilot and which connectors they can use.

Tip: Review your current Microsoft 365 agreement before you add new licenses. This step helps you avoid unexpected costs.

Licensing also affects support and compliance. Premium licenses often include advanced security features and dedicated support. If your organization handles sensitive data, you may want these extra protections. You should also check if your region has special compliance rules. Some industries, like healthcare or finance, require specific licensing for data handling.

You can monitor license usage in the Microsoft 365 Admin Center. This dashboard shows which users have access and how they use Copilot Connectors. Regular reviews help you optimize your investment and ensure everyone has the tools they need.

You should plan your licensing strategy before you roll out Copilot Connectors. This approach helps you control costs, meet compliance needs, and support your business goals. If you have questions, you can contact your Microsoft account representative for guidance.

Copilot Connectors Use Cases

Business Process Automation

You can use Copilot Connectors to automate many business processes. These connectors help you build assistants that handle routine tasks and answer questions. For example:

• A procurement assistant can answer policy questions and check if vendors follow your company’s rules.
• A travel assistant can help employees file expense reports and guide them through approval steps.
• An IT support bot can sort help tickets and offer self-service troubleshooting.

When you use these solutions, you save time on document creation, meeting summaries, and reporting. You also see better writing quality and clearer communication. Many organizations notice that more people use Copilot features each week. Teams finish tasks faster and make fewer mistakes. Internal helpdesk requests often go down because users solve problems on their own.

Knowledge Discovery

Copilot Connectors make it easier for you to find and use information from different places. You can gather data from many systems and create reports or summaries quickly. In the biotech industry, Copilot agents can collect clinical trial data, research reports, and regulatory guidelines. They combine this information into one report for your team. In a law firm, a Copilot agent can pull case files from systems like iManage, NetDocuments, and SharePoint. You get a complete case summary when you need it.

This approach helps you discover knowledge that was once hidden in separate systems. You spend less time searching and more time making decisions.

Industry Scenarios

Healthcare

You can use Copilot Connectors in healthcare to track patient check-ins and manage treatment statuses. These tools help doctors and nurses keep up with both clinical and administrative tasks. You can build apps that improve how you care for patients and run your office.

Finance

In finance, risk analysts use Copilot to create loan evaluation apps. These apps automate data processing and scoring. You get faster decisions and better compliance tracking. This helps your team follow rules and make smart choices.

Manufacturing

Manufacturing teams use Copilot Connectors to monitor machine performance and automate maintenance requests. You can build dashboards that show how machines are working. This leads to better efficiency and higher quality in your products.

Tip: You can connect Copilot to your line-of-business systems and custom databases. This gives you a single place to manage data and automate tasks, no matter your industry.

Best Practices for Copilot Connectors

Implementation Planning

You set the stage for success by planning your Copilot Connectors deployment carefully. Start by evaluating your organization’s readiness. Assess your team’s AI literacy and identify champions who can lead the way. Next, run a pilot program with a small group. Gather feedback on their experience and use it to refine your approach.

Follow these steps for a smooth rollout:

1. Assess readiness: Check if your team understands AI and Copilot basics.
2. Identify champions: Choose people who can support and encourage others.
3. Run a pilot: Test Copilot Connectors with a select group and collect feedback.
4. Integrate technically: Set up connectors, configure access controls, and ensure everything works with your business systems.
5. Manage change: Offer guidance and support as users adapt to new tools.
6. Measure adoption: Track key performance indicators to show value and keep momentum.

Tip: Use Microsoft Entra to secure your data pipelines and monitor connector activity from the start.

Governance Strategies

Strong governance keeps your data safe and your Copilot Connectors running smoothly. You need to track user activity and monitor data access. Set up alerts for policy violations to catch unauthorized actions early.

• Track who uses Copilot and which applications they access.
• Monitor data access to support privacy and security audits.
• Set up alerts for any policy violations.
• Maintain audit trails to help with compliance and investigations.

Data policies play a key role. They block anonymous access and make sure only authenticated users can create and publish copilots. This aligns with your security policies and prevents unauthorized data exposure. Administrators can configure access controls, so only trusted users can publish solutions after IT certification.

Here is a quick overview of governance topics:

Note: Regularly review your governance framework to keep up with organizational changes and new security requirements.

User Training

Effective training helps your team get the most from Copilot Connectors. Start with a strategic alignment workshop to match your organization’s goals with AI capabilities. Offer workshops that focus on discovery, education, and planning. Pilot studies let you test new features and measure their impact over several months.

Ongoing user enablement programs provide continuous support. These programs include onboarding, change management, and tailored education.

Tip: Combine workshops, pilot studies, and ongoing support to build confidence and drive adoption across your organization.

You can transform your Microsoft 365 experience with Copilot Connectors. These tools give you unified data access and boost productivity across your organization. The table below shows how Copilot Connectors deliver measurable value:

To maximize your investment, you should:

• Work with teams to find the best use cases.
• Build proof-of-concepts and offer training.
• Use Copilot Studio and SharePoint Agents for extensibility.
• Integrate data from ERP and CRM systems.
• Track adoption and measure results.

Explore Copilot Connectors to unlock new possibilities and drive business success.

Use this checklist to plan, deploy, secure, and maintain Copilot Connectors.

• Define scope and objectives for Microsoft Copilot Connectors (use cases, data sources, expected outcomes)
• Inventory existing systems, APIs, and data repositories to connect
• Document functional and non-functional requirements (latency, throughput, availability)
• Validate and provision identities and access (service principals, managed identities)
• Configure and test authentication and authorization methods (OAuth, Azure AD)
• Apply least-privilege permissions for connectors and service accounts
• Classify data and define handling policies for sensitive information
• Ensure encryption in transit and at rest for connector data
• Review privacy, compliance, and data residency requirements
• Configure network controls (firewalls, VNET integration, service endpoints)
• Enable logging and monitoring for connector activity and errors
• Set up alerts for failures, suspicious activity, and performance issues
• Perform functional and integration testing in a non-production environment
• Conduct performance and load testing for anticipated workloads
• Define backup, recovery, and failover procedures for connected data
• Establish governance: connector ownership, change management, and approval workflows
• Document connector configuration, endpoints, credentials lifecycle, and runbooks
• Train administrators and users on using and managing Copilot Connectors
• Create an onboarding checklist for adding new connectors and data sources
• Schedule regular review and patching of connector components and dependencies
• Plan periodic security and compliance audits for connectors
• Monitor and optimize costs associated with connectors and data egress
• Define decommissioning process for retired connectors and data removal
• Review connector effectiveness and iterate on improvements regularly

additional resources for microsoft copilot connectors

What are Microsoft Copilot connectors and how do they extend Microsoft?

Microsoft Copilot connectors are integrations that bring external content into Microsoft 365 and copilot experiences so Copilot can access connector content from services like Confluence, MediaWiki, Google services, and custom data stores. They extend Microsoft and partner solutions by making content available to Copilot and improving discoverability for search and copilot search scenarios.

How do connectors interact with Copilot search, search and Microsoft 365 Copilot, and Microsoft Search?

Connectors index connector content and sync it into Microsoft Search and Copilot search contexts so copilot responses and search results can include content from external items. Synced connectors and semantic indexing enable Copilot to surface relevant content in Copilot chat and copilot and microsoft search experiences, improving the relevance of answers and BizChat workflows.

Can admins configure which connectors are available to Copilot and how?

Yes, admins can configure connectors via the Microsoft 365 admin center, Microsoft Graph, or partner portals. Admins can grant permissions, control discoverability, filter which content is indexed, and manage security updates and access policies so sensitive data is protected while making approved content available to copilot connectors.

Are there prebuilt connectors in a connectors gallery and can I see Copilot connectors before using them?

Microsoft and partner ecosystems provide a connectors gallery with many prebuilt options, including power platform connectors and connectors for popular services. You can see Copilot connectors in documentation and preview environments, and Microsoft Learn and additional resources list available connectors and guidance on how to deploy them.

How do I create custom connectors or custom agents to bring external data in real time?

You can create custom connectors using the Microsoft Graph Connector framework, Power Platform connectors, or by building custom agents that implement the model context protocol. Custom connectors can push data into Microsoft 365 or provide data in real time via APIs and Azure Services. Microsoft Learn and technical support resources provide step-by-step examples to create custom connectors.

What is semantic indexing and how does it affect copilot responses?

Semantic indexing enriches connector content with embeddings and metadata so search and Copilot can understand meaning and context, not just keywords. This improves Copilot responses’ relevance and helps Copilot generate summaries or filter results by topic, date, or security label.

Can Copilot connectors include people data, and what is “Copilot connectors for people data”?

Yes, specialized connectors for people data let Copilot surface organizational profiles, reporting lines, and contact details. Copilot connectors for people data must be configured with care for privacy and security updates; admins can configure access and filters to ensure only appropriate people information is available to Copilot.

How do connectors handle content from external sources like Confluence or MediaWiki and maintain discoverability?

Connectors index content from external items such as Confluence and MediaWiki, extract metadata, and map it into Microsoft Search so content from external sources becomes searchable and discoverable in Microsoft 365 and Copilot experiences. Discoverability can be tuned with filters, tags, and semantic indexing.

Do connectors support real time data and data in real time for use in copilot chat or BizChat?

Some connectors support near real time synchronization or push notifications via Azure Services and webhooks so Copilot can access data in real time. For truly real time workflows in copilot chat or BizChat, build connectors that stream updates or implement APIs that provide live context to custom agents.

How are security updates and technical support handled for connectors?

Microsoft and partner connectors follow security update practices and compliance standards; administrators receive security updates and guidance through the Microsoft 365 security center. For issues, technical support is available from Microsoft Learn resources, partner support channels, and Microsoft technical support depending on the connector’s source.

Will Copilot ever miss content from external systems and how can I reduce misses?

Copilot can miss content if connectors are misconfigured, not authorized, or if content isn’t indexed due to filters or sync frequency. To reduce misses, verify connector content mapping, adjust filters, enable synced connectors or real time updates, and use semantic indexing so search and copilot responses surface relevant external items.

Can I filter what Copilot returns from connector content and enforce compliance?

Yes, admins can configure filters, sensitivity labels, and access controls to limit which connector content is indexed and returned in copilot responses. Filtering helps enforce compliance and ensures Copilot does not expose restricted information in search and copilot chat scenarios.

What about integrating Google Services and other third‑party platforms with Copilot?

Integrations with Google services and other third‑party platforms are possible through prebuilt connectors, partner connectors, or by creating custom connectors. These solutions bring content from external systems into Microsoft Search and Copilot, subject to authentication and security policies.

Where can I find additional resources and learning material about Copilot connectors?

Use Microsoft Learn, technical support articles, the connectors gallery, and documentation for search and copilot. Additional resources include tutorials on creating custom connectors, examples for model context protocol integration, and guidance on extending Microsoft with partner solutions.

How do Power Platform connectors relate to Microsoft Copilot connectors?

Power Platform connectors let you connect apps and flows to external systems and can be used to create or enrich connector content for Copilot. They make it easier to bring external data into Microsoft 365 and enable automation that supports copilot search and copilot chat scenarios.

Can I customize how Copilot uses connector content in Copilot chat or Copilot search results?

Yes, by creating custom agents, configuring semantic indexing, and tuning connector content mappings you can influence how Copilot uses external content. Admins and developers can control ranking signals, filters, and which fields are surfaced in copilot responses or search and microsoft 365 copilot outputs.

How do licensing, preview features, and availability affect using Copilot connectors?

Some connectors or features may be in preview or have specific licensing requirements. Availability can vary by tenant and region; check Microsoft Learn and the product roadmap for preview announcements and licensing details to ensure connector features are available to your organization.

Are there best practices for making connector content useful and discoverable to Copilot?

Yes. Best practices include applying clear metadata, using semantic indexing, keeping content updated, configuring filters and security labels, and testing in preview environments. These steps help Copilot surface accurate, relevant connector content and improve search and copilot responses.

What is the role of model context protocol when creating custom agents that use connectors?

The model context protocol helps custom agents provide structured context to language models, enabling Copilot to make better use of connector content. Implementing the protocol ensures consistent context formatting and improves the quality of copilot responses that reference external items.

How can I see Copilot connectors in action or test them before rollout?

You can test connectors in a sandbox or preview tenant, use Microsoft Learn labs, and try sample queries in Copilot chat or copilot search to evaluate how connector content appears. Use diagnostic tools and logs to verify syncing, semantic indexing, and that admins can configure settings correctly.

🚀 Want to be part of m365.fm?

Then stop just listening… and start showing up.

👉 Connect with me on LinkedIn and let’s make something happen:

• 🎙️ Be a podcast guest and share your story
• 🎧 Host your own episode (yes, seriously)
• 💡 Pitch topics the community actually wants to hear
• 🌍 Build your personal brand in the Microsoft 365 space

This isn’t just a podcast — it’s a platform for people who take action.

🔥 Most people wait. The best ones don’t.

👉 Connect with me on LinkedIn and send me a message:
“I want in”

Let’s build something awesome 👊