Hi @NA-20020143-0,
Let's analyse the error message it shows:
"Unable to configure knowledge source". For this error, before going any further we need to make sure connection is successful or not:
Knowledge Source
Type: Azure SQL Database
Connection status: Successful – preview data is visible inside Copilot Studio.
Permissions: Let's make sure user profile used to connect to Azure SQL server have admin permission on Azure and it's also the same account that created the database.
The second part of the error says: "We encountered an issue while setting up this knowledge source."
Do we really know who this "We" are? is this microsoft or the team who is working with the Co-Pilot and Azure SQL? It's microsfot based on the error message. Since microsoft has encountered an issue - it's a big issue and I beleve they have already seen this issue on their dashbaord, no? If that is the case, what they say next?
"Please try again" : As they said to try again, it means a lot. You need to log-out from everything, re-login, refresh everything and try build the connection again. But it is not said "Please try after 10 minutes or 10 days!" That's a message that ignites users to be impatient! So, in my case what I have expereinced, it takes 10-15 minutes or even 2 hours, and if bad luck triggers you have to be persistant with support ticket until the issue is resolved! So, do your best to troubleshoot any way, add knowledge source again and see if any technical error message is shown. All I am sayin about, you have to build a connection first, you don't need to care about knowledge schema, size of knowledge source, any query optimization!
An then the error says: "If the problme persisits, contact your administrator." This is the vital part of the message- it abandons us in an unknonwn territory! Let's first contact the asministrator - and luckily if you are the administrator - go grab helth check - any error, any message, any RIP is there. If not - don't worry to open up a support ticket asap.
Bare minimum basics I can suggest here are:
1. Please trace back what lastly got changed and modififed.
2. Sometimes platform updates can cause temporary issues; try removing and re-adding the knowledge source
3. Double-check that the user or service principal has the necessary read permissions on the database and tables.
4. Ensure that the Azure SQL server firewall rules allow connections from the Power Platform service IP ranges. Confirm there are no recent network restrictions or VPN changes blocking access.
5. Check if the credentials or authentication method (e.g., service principal) used by the connector have expired or changed.
Last note: Please remember once we are in MS platform, these are not we who do changes, We + MS do the changes!
I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!
