Unable to Retrieve Attachments or Images from SharePoint List Using Web API
We have been developing a banner app for SharePoint but encountered an issue where we are unable to access images or attachments from the list created using the Web API. The endpoint we used is: https://oursharepoint.com/sites/Test/_api/web/lists/getbytitle('Banner')/items While we can successfully access other list columns, we are unable to retrieve attachments or images through this method. Interestingly, we were able to access them on our test SharePoint site.
displayDialogAsync shows empty dialog box
Hi, I am using my Outlook add-in to display a dialog box. However, if I usedisplayInIframe:true then the contents of the dialog box won't load. After a few seconds, it will display the attached error in the dialog box and I'll see an error in the console that says "[Report Only] This document requires 'TrustedScript' assignment." I have tried to see if there's any error by using a callback, but that always says that it succeeded. The URL is on the same domain as the code hosted by the add-in. I am getting this issue in OWA on Chrome and Firefox as well as PWA. In classic Outlook the content doesn't load either, but I also don't see that error in the console. Office.context.ui.displayDialogAsync(url, {height: 30, width: 20, promptBeforeOpen: false, displayInIframe: true}, function (result) { console.log('Callback result:'); console.log(result); } );SSO issues in Word and Excel, but not Outlook
Hi, Strange issue started a month ago at a customer site. They use RDS with Office 365 installed. Historically this has been working fine, then it randomly stopped signing in properly for all users. We can't point it down to anything specific however. Network / User / Settings all look good. What is strange is on first login to Outlook, it says it's done SSO but says unlicensed. A simple restart then would show it licensed. We have managed to work round that issue by saving the license folder \appdata\local\microsoft\office\ to the UPD. So for this, a month ago, new and existing users would just sign in and it worked. Then something changed and users were being asked to sign in every time. So we have made this change to include \appdata\local to the UPD - now users only see this problem once (a month). While not as good as it was a month ago, it is acceptable. However, and this is what I need help with. SSO is NOT working at all from Word / Excel. Open Word Blank Micrsoft Sign In box pops up. You have to type username and hit enter You then have to type your password and hit Sign In That popup then goes away, but at the tope right of Word, it still shows "Sign In". When you go to Account, it still has a Sign in box. BUT... if you now close and reopen word, both of those show the signed in user. The problem here is that this doesn't persist over the UPD, so happens every time the users open Word or Excel. As this is used by a business app to open docs, it's actually breaking the process and we need to fix this. I have been having a look at SSO info, because it feels like something fairly low level has changed with how this works, but can't find anything helpful, hence posting here after about a month of searching and trying things. It's not very helpful when you have MS links like: How to use Remote Connectivity Analyzer to troubleshoot single sign-on issues for Microsoft 365, Azure, or Intune https://learn.microsoft.com/en-us/microsoft-365/troubleshoot/active-directory/single-sign-on-issues How to run Remote Connectivity Analyzer to test SSO authentication To run Remote Connectivity Analyzer to test SSO authentication, follow these steps: Open a web browser, and then browse tohttps://www.testconnectivity.microsoft.com/tests/SingleSignOn/input. However, that page just hangs with LOADING written on it. Then on the change notes for this page we see that it was removed in 2022! Version 4.0.15 (October 2022) Removed the Single Sign-on Test now that basic authentication in Exchange Online is being disabled. Quick note on the setup. AD is synced to Entra using Entra Connect (Password Hash Sync + SSO enabled), latest version. SSO URLs are added to Internet trusted sites as per setup instructions. Network has been tested and all URLS accessible and working for the user. User is on RDS on fully updated Server 2016 and is on the latest Office 365 app updates. So I guess my first question is: 1) Does SSO still work for Word and Excel? Is it a realistic expectation that the user will sign in to the PC and then Word and Excel will automatically sign in for the user (proper seamless single sign on) like it was doing only a month or so ago? 2) What can I do to test and troubleshoot this if it should be working? I have been trying for a month, so I have already tried a lot of things. But maybe I am missing some tests? Any info to help get this working again (or that it's no longer possible and we missed that instruction from MS) would be ideal. Thanks in advance
Office bypassing Target Version set by Intune
Ok so I was managing my Microsoft patches through Intune. A while back Microsoft sent out this message…. https://docs.microsoft.com/en-us/DeployOffice/other/devices-updating-monthly-enterprise-channel I believe I had opted out but recently our machines have started updating to the Monthly channel. So if this is true that we are now moved to Monthly channel how do we control it moving forward? I have done some of my own research and came across the following but still not sure what is what. If you log in here - https://admin.microsoft.com Go to settings, org settings, Office installation updates. You have some items here. If you click on Organization profile in the same window you have "Release preferences" If you log in here - https://config.office.com Go to servicing, Monthly enterprise, settings. You can choose criteria, rollout, etc Also I know in the past to troubleshoot a single device the reg keys you wanted to look at were: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\office\16.0\common\officeupdate Updatebranch updatedeadline updatetargetversion HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration CDNBaseURL ClientversionToReport UpdateChannel Though I think now that it is managed from https://config.office.com this is the new key to look @ HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\cloud\office\16.0\Common\officeupdate instead of the old one HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\office\16.0\common\officeupdate Any input on the above would be great.
Microsoft 365 Apps for Enterprise - Auto sign in and Activation using Domain User Credentials
Hi, I use shared computer activation butevery new user who sign-in for the first time required to login with their account and do manual activation.it burdens users all the time to do this. there is a way to do when a user logs in to Microsoft 365 Apps he will do it automatically in shared computer activation without him having to do all that. i would love a solution using domain user credentials. Rodriguez_591
O365 not updated from MECM
We have one XML for deploying O365. When i install it on W10/11 machine it download updates from MECM. But old installations on servers start downloading updates from internet 1-2 month ago. I find some strange things hereMicrosoft 365 Apps admin center (office.com) We use this 3/4 year ago to migrate all devices toMonthly Enterprise Channel. Then i exclude all devices. Now i check servers are again managed by this ..... When i install O365 to new server all is working fine. How to tell existing servers to take updates from MECM? I try full uninstall, reinstall nothing work. It not problem of MECM deployment, on new servers where O365 never exist its working fine. How to get out from this terribleMicrosoft 365 Apps admin center (office.com)settings?M365 apps for enterprises subscription info missing in produict info
HI Team, In our organization, we have deployed the M365 apps 32 bit through ODT and manage via cloud updates. We do have E3 license activated. When reviewing the product information, I don't get the M365 apps for enterprises subscription inform. I have attached the screenshot for the difference. Is that anything, we need to correct?
Why is it possible to create broken 365 app config files?
I've been trying to configure Intune win32 deployable Office & 365 applications for my company, and it's been driving me insane. I used the deployment tool and the config creator to create deployments for Office, Visio, & Project. Office worked fine, but Visio & Project have not been working at all. Just failing instantly. I've just done hours of investigating and trial-and-error and have found the problem: Visio and Project are not available in en-gb language. I tried installing through Intune (instant fail), then directly from the setup.exe with the config: instant fail. Neither gave any useful error information. I then changed the config to show the installation display (which was hidden, as it's meant for mass deployment), which then said the language is not compatible. I thought that had to be a mistake, why wouldn't British English work? I then tried making it the same language as the device's Office installation (also en-gb) using MatchInstalled, hoping it was just some bug - this seemed to work, it didn't show the language error any more! It was now showing a connectivity error. Ugh. I spent a while trying to diagnose this before changing the language in the config to en-us, and it worked instantly. Why was I able to create the configs for Visio and Project using the official Microsoft tool with en-gb as the language when that was never going to work?Microsoft Inventory Unsupported Builds
Recently we have begun using the Microsoft 365 Apps admin center to update our company's O365 Apps accounts. Some of the users added in the inventory have "Unsupported Builds". Further investigations into this topic have come up empty and I was wondering what these unsupported builds mean for the user as well as steps to take to get them running a build that is supported.