I did a little more digging and found further information:

1. Third-Party Libraries: Reading Excel files in Databricks often requires using third-party libraries such as com.crealytics:spark-excel. However, in Unity Catalog-enabled environments, there are restrictions on third-party libraries due to security isolation concerns. For example, the com.crealytics:spark-excel library may require additional permissions, such as granting "ANY FILE" access, to function correctly in a Unity Catalog environment. Without these explicit permissions, errors may occur when attempting to read Excel files.
2. Pandas Workaround: While third-party libraries might have access restrictions, the pandas.read_excel function can typically be used to read Excel files without such issues, as it does not rely on the same security isolation mechanisms.
3. Unity Catalog Volumes Limitations: Direct writes or non-sequential access for Excel files (e.g., .xlsx format) are not supported in Unity Catalog volumes. Users need to perform operations on local storage first and then copy the files to Unity Catalog volumes as a workaround.

• Granting Permissions: If using com.crealytics:spark-excel, you may need to ensure the correct permissions are in place (e.g., granting "ANY FILE" on external locations). Consult with your Unity Catalog administrator to verify or adjust permissions.
• Intermediate Local File Operations: For writing Excel files, consider writing them locally using libraries like xlsxwriter and moving them to Unity Catalog volumes after the operation is complete: ```python from shutil import copyfile import xlsxwriter
  # Write Excel file locally workbook = xlsxwriter.Workbook('/local_disk0/tmp/excel.xlsx') worksheet = workbook.add_worksheet() worksheet.write(0, 0, "Key") worksheet.write(0, 1, "Value") workbook.close()
  # Copy to Unity Catalog volume copyfile('/local_disk0/tmp/excel.xlsx', '/Volumes/my_catalog/my_schema/my_volume/excel.xlsx') ```