You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: netapp-neo/USER_QUICKSTART_M365.md
+11-97Lines changed: 11 additions & 97 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,75 +1,24 @@
1
1
# NetApp Neo deployment User Quick Start Guide (v3.x)
2
2
3
-
> \[!IMPORTANT\]
4
-
>NetApp Neo for M365 Copilot is currently in **Private Preview**. This means that the connector is not yet fully supported and may have some limitations. The connector requires a license to activate. You can request access to the connector by joining the Early Access Program (EAP). Please book a meeting with the following link to join the EAP: [Book a meeting with NetApp](https://outlook.office.com/bookwithme/user/[email protected]/meetingtype/nm-mXkp-TUO1CdzOmFfIBw2?anonymous&ismsaljsauthenabled&ep=mlink).
5
-
6
-
> \[!IMPORTANT\]
7
-
> AWS ECS (Fargate) is NOT supported. This is due to the containers being unable to mount shares to the container(s) - a critical requirement of NetApp Neo.
3
+
> \[!IMPORTANT\]
4
+
>
5
+
> -**THIS GUIDE HAS BEEN SUPERSEDED.** Please refer to the latest version of this guide at: [NetApp Project Neo Documentation](https://netapp.github.io/netapp-connector-docs/)
6
+
> - NetApp Neo for M365 Copilot is currently in **Private Preview**. This means that the connector is not yet fully supported and may have some limitations. The connector requires a license to activate. You can request access to the connector by joining the Early Access Program (EAP). Please book a meeting with the following link to join the EAP: [Book a meeting with NetApp](https://outlook.office.com/bookwithme/user/[email protected]/meetingtype/nm-mXkp-TUO1CdzOmFfIBw2?anonymous&ismsaljsauthenabled&ep=mlink).
7
+
> -AWS ECS (Fargate) is NOT supported. This is due to the containers being unable to mount shares to the container(s) - a critical requirement of NetApp Neo.
8
8
9
9
## 1\. Prerequisites
10
10
11
-
### Network Requirements
12
-
13
-
-**Port 443** open for outbound traffic to the MS Graph API
14
-
-**Port 8080** open for internal management of the connector
15
-
-**Port 445** open for SMB file share access
16
-
- SMB File Share(s) must be routable to the connector
17
-
18
-
### Software Requirements
19
-
20
-
- Microsoft 365 Copilot License
21
-
- Docker installed on the machine where the connector will be deployed
22
-
- Access to the offline tar image of the connector
23
-
- (Optional) Docker Compose installed on the machine where the connector will be deployed
24
-
- (Optional) Access to a Kubernetes cluster for deployment
25
-
26
-
### Register the connector in Azure Entra
27
-
28
-
In order for the connector to be able to securely communicate with M365 Copilot.
29
-
30
-

31
-
32
-
1. Navigate to the Azure Entra portal and select "Add" and select the "App Registration" option.
33
-
2. Fill in the required fields and click "Register". (No Redirect URI is required)
34
-
3. Copy the Application (client) ID and Directory (tenant) ID from the Overview page.
35
-
4. Navigate to the "API permissions" page and select "Add a permission".
36
-
5. Select "Microsoft Graph" and then "Application permissions".
37
-
6. Search for "ExternalConnection.ReadWrite.OwnedBy" and select the checkbox.
38
-
7. Search for "ExternalItem.ReadWrite.OwnedBy" and select the checkbox.
39
-
8. Search for "User.Read" and select the checkbox.
40
-
9. Search for "User.Read.All" and select the checkbox.
41
-
10. Search for "Group.Read.All" and select the checkbox
42
-
11. Click "Add permissions".
43
-
12. Click "Graph admin consent for (tenant)" and click "Yes".
44
-
13. Navigate to the "Certificates & secrets" page and click "New client secret".
45
-
14. Fill in the required fields and click "Add".
46
-
15. Copy the value of the client secret.
47
-
48
-
You have successfully registered the connector in Azure ENTRA. You will need the Application ID, Directory ID, and Client Secret for the next steps.
49
-
11
+
Please refer to the latest prerequisites here: [Prerequisites](https://netapp.github.io/netapp-connector-docs/prerequisites.html)
50
12
51
13
## 2\. Getting Started
52
14
53
-
The easiest way to get started is by using the pre-built container image. You can run the connector using Docker/Podman or deploy it to a Kubernetes cluster using Helm.
15
+
Please refer to the latest quickstart instructions here: [Quick Start](https://netapp.github.io/netapp-connector-docs/quick-start.html)
-**PostgreSQL**: For production deployments with high availability (Recommended)
60
-
-**MySQL**: Alternative production database option
19
+
Please refer to the latest database options here: [Database Options](https://netapp.github.io/netapp-connector-docs/prerequisites.html#database-options)
61
20
62
-
To use PostgreSQL or MySQL, set the `DATABASE_URL` environment variable:
The connector will be deployed and will be accessible on port 8080. You can access the API documentation at `http://localhost:8080/docs`.
137
53
138
54
Trouble deploying the connector? Check the [Troubleshooting](#troubleshooting) section for common issues.
139
55
140
-
141
56
### Deploy using Kubernetes and Helm
142
57
143
58
If you are using Kubernetes, you can deploy the connector using Helm. Please refer to the [Helm Deployment](../charts/netapp-copilot-connector/README.md"charts/netapp-copilot-connector/README.md") document for more information.
0 commit comments