It's working reliably for me with other apps, but will not work with Microsoft Word (using word version 16.10 if it matters).
I don't use this but the Copy Bible Verse tool works great.
It still works OK with Word 2011 and the latest version of Pages. Usually when that feature does not work, it does not work at all with any app. It's possible the Microsoft update may have changed something (nothing unusual about that). Have you tried opening the "Services" menu while in Word 2016 to see if the "Replace with Passage" option has been chosen or if it's even there?
In Christ,
Charles
Yes, it's still on the services menu, it just doesn't work with the latest version of Word. It does work in other apps.
It still works OK with Word 2011 and the latest version of Pages. Usually when that feature does not work, it does not work at all with any app. It's possible the Microsoft update may have changed something (nothing unusual about that). Have you tried opening the "Services" menu while in Word 2016 to see if the "Replace with Passage" option has been chosen or if it's even there? Yes, it's still on the services menu, it just doesn't work with the latest version of Word. It does work in other apps.
I can confirm that it is no longer working with the latest version of Microsoft Word (16.11) and Verbum (7.13). What's interesting is that other services seem to work (such as "Add Text to Evernote" and a few others I tried.)
I agree with the original poster in encouraging Faithlife to take a look at this bug. At the very least, let us know what the issue is so we can interface with Microsoft and pinpoint the problem. The "Replace with Passage" service is absolutely indispensable to many of us who regularly prepare sermons, academic writing, blog posts, and more in Microsoft Word.
Also, this link might help anyone who needs this functionality while everything is sorted out:
https://support.office.com/en-us/article/how-to-go-back-to-office-2016-for-mac-15-xx-versions-from-16-xx-e88ed6c8-6fb4-40a1-9540-529000d3d20f
The good and helpful folks at Microsoft were quite receptive to this bug report that I filed with them directly. They were able to reproduce the issue and marked it as a bug on their end. Hopefully, that means it will be fixed soon.