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/DEPLOY-V2.md
+28-26Lines changed: 28 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,19 +45,20 @@ In order for the connector to be able to securely communicate with M365 Copilot.
45
45
14. Fill in the required fields and click "Add".
46
46
15. Copy the value of the client secret.
47
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.
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
49
50
50
## 2\. Getting Started
51
51
52
52
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.
| `main.name` | The base name for all created resources. | `netapp-connector-main` |
218
+
| `main.replicaCount` | Number of connector pods to run. Only 1 is supported. | `1` |
219
+
| `main.image.repository` | The container image repository. | `ghcr.io/netapp/netapp-copilot-connector` |
220
+
| `main.image.tag` | The container image tag. If empty, defaults to the chart's `appVersion`. | `""` |
221
+
| `main.image.pullPolicy` | The image pull policy. | `Always` |
222
+
| `main.service.type` | The type of Kubernetes service to create. | `ClusterIP` |
223
+
| `main.service.port` | The port exposed by the service and container. | `8080` |
224
+
| `main.ingress.enabled` | If true, create an Ingress resource. | `false` |
225
+
| `main.ingress.host` | The hostname for the Ingress rule. Required if Ingress is enabled. | `nil` |
226
+
| `main.ingress.path` | The path for the Ingress rule. | `/` |
227
+
| `main.ingress.pathType` | The path type for the Ingress rule (`Prefix`, `Exact`, `ImplementationSpecific`). | `Prefix` |
228
+
| `main.ingress.className` | The `ingressClassName` to associate with the Ingress. | `""` |
229
+
| `main.ingress.tls` | Ingress TLS configuration (list of objects with `secretName` and `hosts`). | `[]` |
230
+
| `main.persistence.enabled` | If true, create a `PersistentVolumeClaim`. | `true` |
231
+
| `main.persistence.accessMode` | The access mode for the PVC. | `ReadWriteOnce` |
232
+
| `main.persistence.size` | The size of the persistent volume. | `1Gi` |
233
+
| `main.persistence.mountPath` | The path inside the container where the volume is mounted. | `/app/data` |
234
+
| `main.env.*` | Non-sensitive environment variables. See `values.yaml` for all options. | (various) |
235
+
| `main.credentials.*` | Sensitive credentials stored in a Secret. **Must be provided by the user.** | (placeholders) |
234
236
235
237
---
236
-
For more information, see the official [Helm documentation](https://helm.sh/docs/) and [Kubernetes documentation](https://kubernetes.io/docs/home/).
237
-
238
238
239
+
For more information, see the official [Helm documentation](https://helm.sh/docs/) and [Kubernetes documentation](https://kubernetes.io/docs/home/).
239
240
240
241
# 3\. Initial Setup and First Admin User
241
242
@@ -327,6 +328,7 @@ You can monitor the crawl progress through:
327
328
1. **Visit the Microsoft 365 Admin Center**: Go to [Search and Intelligence](https://admin.microsoft.com/Adminportal/Home?source=applauncher#/MicrosoftSearch/connectors)
328
329
2. **Enable Connector Results**: Ensure you have selected **_Include Connector Results_** for NetApp Neo
329
330
3. **Test in Microsoft 365 Copilot**: Try searching for content from your indexed files using natural language queries
331
+
4. **Control Access**: Verify that search results respect the original file permissions from your SMB shares. Item level permissions will be attempted to be preserved based on the ACLs read during the crawl, however this may not always be possible depending on your environment and configuration. It is recommended to test access with different user accounts to ensure proper security. In addition to item level permissions, you can also configure (recommended) broader access controls using Microsoft Entra groups and roles using the Microsoft 365 Admin Center -> Copilot Connectors settings -> Staging Permissions to control users and groups that can access content from the connector.
330
332
331
333

Copy file name to clipboardExpand all lines: netapp-neo/README.md
+1-11Lines changed: 1 addition & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,17 +29,7 @@ The NetApp Neo: Connector for M365 Copilot is a containerized solution that enab
29
29
30
30
## Getting Started
31
31
32
-
Want to get up and running quickly? Head over to
33
-
34
-
- the Neo v3.x [User Quickstart for M365](./USER_QUICKSTART_M365.md) guide for a step-by-step guide to deploying the connector and connecting your first share.
35
-
- the Neo v2.x (**phasing out**) [User Quickstart for M365](./DEPLOY-V2.md) guide for a step-by-step guide to deploying the connector and connecting your first share.
36
-
37
-
## Security Information
38
-
39
-
The NetApp Neo: Connector for M365 Copilot is designed with security in mind. All relevant security information is available in the [Security Information](SECURITY.md) document. This includes information on how the connector handles data, how it communicates with Microsoft Graph, and how it is secured.
40
-
41
-
## Frequently Asked Questions (FAQ)
42
-
Most frequently asked questions are available in our [NEO FAQ](FAQ.md)
32
+
Want to get up and running quickly? Head over to [User Documentation](https://netapp.github.io/netapp-connector-docs/)
0 commit comments