On the editing side, Confluence Cloud won't co-author an attached Office file in place, the file is stored outside Confluence, so whoever saves last ends up on top. If you want genuine simultaneous editing, the practical route is to keep the file in OneDrive/SharePoint or Google Drive and embed or link it on the page, so the co-authoring happens in Microsoft's or Google's own editor where the merge is handled for you. If the content can just live in Confluence, pasting it in as a page or table (or using a spreadsheet macro app) turns it into native collaborative content and sidesteps the whole attachment problem.
On residency, Forge apps run on Atlassian's own infrastructure and follow your site's data residency, so if EU/Germany matters, filter the Marketplace for Runs on Atlassian / Cloud Fortified.
If the real goal is the second half of your ask, stop two people editing at once and overwriting each other, that's a lock/check-out model, which Confluence has no native equivalent for. Sentinel Vault does exactly that for attachments, you seal a file while you work on it, everyone else sees it's held, and if something does get changed out of band it auto-reverts to the sealed version. Full disclosure: I'm on the LeanZero team.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.