AWS Q Sharepoint Connector - Does it really work?

Have been working with an instance in AWS Q Business:

• Setup a connector to a SharePoint Online collection, using OAuth 2.0 certification. No issues.
• Crawled and Indexed documents with various types of field mappings, including all possible options. Multiple syncs with various combinations of "document title" or "sp__title", etc.
• Documents indexed and crawled successfully. No errors thrown.
• No response generated for any kind of question due to no documents retrieved, "...could not find relevant information ..."
• Copied document collection to S3, run data source with defaults. Works perfect.
• Confusion....
• Maybe ACL issues don't throw errors during indexing but still prevent responses...?
• ACL permissions from Azure side match AWS documentation but the issue persists.
• Does AWS Q actually have the ability to retrieve documents from SharePoint and generate answers?

So far no combination of field mapping for the Sharepoint collection works, including multiple copies of the connector with different field mappings and single connectors with all possible field mappings. Entirely new Q instances set up with only a single connector have identical issue. Since the S3 document collection works correctly that seems to rule out VPC or field mapping issues because both connectors throw no errors or produce suspicious Cloudwatch logs during sync and use an identical setup. It seems odd that the only field mapping for S3 is "s3_document_id" and it just works out of the box but Sharepoint has multiple mappings and doesn't work at all. As mentioned, no CloudWatch logs indicate that there are issue with access or indexing or crawling. Any kind of assistance or a good reference to a description of how to get this workflow working correctly would be appreciated. Many Thanks.