We identify a potential bug in either DBFS or Pandas that when writting a dataframe using Pandas `to_csv`, `to_parquet`, `to_pickle` etc to a mounted ADLS location with read-only service principle didn't throw permission deny exceptions. However, methods like `to_html`, `to_latex`, `to_excel` Spark API and Python API correctly throw the error. See attached notebook screenshot. I'm guessing the issue is more likely on the Pandas IO implementation that interact with DBFS but would like to notify Databricks since how DBFS underlying implementation with cloud object is not clear.