Forum Discussion
Solved
Internal linking not possible: We only support linking to files in your own organization.
Since few days we got this error message if we try to add a link to a file or document on a sharepoint site: "We only support linking to files in your own organization." which option thr...
Hello Everyone,
First, apologies for any inconveniences during this investigation.
I believe we have identified the issue and applied a fix early today.
If you are still seeing any issues with this functionality please let me know.
Regards,
Sam
simuuh Melinda Grant Jimmy Hang Sarnst
Product Owner has provided the following feedback
"This issue has been identified as a bug, and the product team is working on the fix now. I will monitor the progress and keep you all updated."
I have tested this issue against the following web parts and all are impacted.
- Image
- File Viewer
- Image Gallery
Experiencing the same issue, any updates today?
Is there any public board where it is possible to follow this issue? There's no notice of it in our admin center regarding service health.I already have a ticket raised - they have identified this as a bug but have yet to provide a ETA for fix. They confirmed the fix will apply to the File Viewer, Image & Image Gallery web parts.
"Yes the bug info has included the image issue. Thanks for updating the information in the community.
The bug fix may take a little long time, and currently I haven’t got ETA for the fix."
I am going to put pressure on providing an ETA - as this is something that was working, a change has been made and now it is not working as intended.
I have asked the following in my Ticket
ETA for fix – Can this be provided – these were working web parts:
A change to SPO web parts has broken them – a little nervous that changes can be made to Office 365 that effectively break the functionality and then it could be days/weeks before it is fixed, what was the QA/Testing process involved – how did this bug get into production.
Could these answers be provided to provide assurance that steps have been taken to prevent these things from happening again e.g. improved QA/Testing process.
NiclasDahl only way I think is to raise a support ticket in Office 365. I just created one #17146737, maybe MS will aknowledge this as a BUG if more of us report it in.
