Search Configuration for Azure Files
Before you start. This page assumes you have already set up your Azure Files source for analysis, as described in Configure Shinydocs Pro Control Center for Azure Files (Azure file share). That page includes these Search steps, so if you followed all of it, Search is already set up.
Search can check each person’s Azure Files permissions. People sign in to Microsoft from Search, and see only results they have access to. Search uses a client secret, redirect URIs and delegated permissions on the same app registration you created for analysis.
Create a client secretIn the Azure portal, open the Shinydocs Pro app registration and select Certificates & secrets, then the Client secrets tab.
- Click + New client secret
- In the Add a client secret panel, add a description of your choice
- Set it to expire in 12 months or longer.
This is a good time to schedule a reminder for the expiry, as Shinydocs Pro will also need the new secret key when this one expires. - Click Add.
- Copy the secret key to a safe location, as you will not be able to retrieve it later.
Still in the Azure portal Shinydocs application registration, now you will set up the redirect URIs for authentication.
- Navigate to the Authentication tab in the application registration Unknown Attachment
- Web > Redirect URIs
- This set up will be for the server running Shinydocs Pro Search using it’s hostname. You can update these settings later when/if you set up your fully qualified domain name in your DNS.
- Redirect URIs (Web platform):
https://<shinydocs pro server host name>:9701/oauth/authorized- e.g.
https://shinyvm:9701/oauth/authorized - If users reach Control Center by its full domain name, add that as well, e.g.
https://shinyvm.contoso.com:9701/oauth/authorized
- e.g.
https://localhost:9701/oauth/authorized
/oauth/authorizedadded. Include the port, unless your DNS or proxy removes it.
Now that the Shinydocs Application has been registered with Azure, it’s time to apply permissions to access content within Azure Files.
- From the sidebar menu, select API permissions Unknown Attachment
- Select + Add a permission Unknown Attachment
- Select Microsoft Graph: Unknown Attachment
- Then, select Delegated permissions Unknown Attachment
- Add the following delegated permissions
User.Read
Type:Delegatedoffline_acccess
Type:Delegatedopenid
Type:Delegatedprofile
Type:Delegated
- Click Add permissions
- Select + Add a permission again
- Select APIs my organization uses and search for Azure Storage Unknown Attachment
- Then, select Delegated permissions and check the box for user_impersonation Unknown Attachment
- Click add permissions.
- Select Grant admin consent for [tenant], confirm when prompted
- Go to Sources, find the group for the connection, and select Edit. You can also go to Settings > Connections, choose the connector, and select Edit connection.
- Search Authentication Type: select Protected - OAuth2, then fill in: Unknown Attachment
- Client Id: the Application (client) ID from your app registration.
- Client Secret: the client secret from your app registration.
- Login/Authorize Endpoint and Token Endpoint: replace
commonwith your Tenant ID, for examplehttps://login.microsoftonline.com/<tenant-id>/oauth2/v2.0/authorizeand.../oauth2/v2.0/token. - Redirect URL: the address users reach Shinydocs Search on, as domain and port only, for example
https://search.contoso.com:9701.https://localhost:9701works for testing on the server itself./oauth/authorizedis added automatically. This URL with/oauth/authorizedmust match a redirect URI on the app registration in Microsoft Entra ID exactly.
- Select Save changes. Control Center checks the connection through an agent before saving, so an agent must be running. It doesn’t check the Client Secret, so sign in to Search afterwards to make sure it works.
If the source uses Protected - OAuth2 for Search, replace its Client secret under Search Authentication Type in the same dialog as above. Control Center doesn’t check this secret when you save, so sign in to Search afterwards to make sure it works.
Before you start. This page assumes you have already set up your Azure Files source for analysis, as described in