Office 365 connector setup

Portal User asked a question.

May 22, 2018 at 7:00 AM

I am trying to setup the Office 365 Connector. I have the instructions but I may be missing something.

I have the Office / Portal Azure side all setup.

Trying to enter the info into the Connector Configuration and have a couple questions.

1. API Endpoint , does something need to be setup for this or is it already there? I entered the SLM server name, http://<SLMServerNAME>/API.

2. Username for SLM Config? Which one does it want? My service account. a regular AD account? When I add my AD account and click Get Customer I get an error pop up, Failed to get customer, No Customer returned. What customer is it looking for and from where?

Can't get past this part.

Thanks,

Portal User
8 years ago
Hello, I already create the users but still have this message in my log: 2019-01-14 13:50:17,833 [1] ERROR SnowSoftware.ExternalDataProvider.Providers.Office365.Properties [()] [()] - Failed when trying to fetch customer from SLM API. => No customer returned :: System.Exception: No customer returned any ideas?
Expand Post
Viktors
8 years ago
Hi ‌. Firstly you need to create a user from the SMACC side, which has API users role: This user will be used for Office365 connector. For API endpoint you will need to use http:// <SLMServerNAME>/API : Best regards, Viktors
Expand Post
- Portal User
  8 years ago
  Thank you both, that got me past that part. Wish SNOW would add specific things like this to the documentation. Too much is assumed. On to the next step. I added the o365 username and password I use to log in on the Portal.Microsoft.com. But I get this error next when I click on Test Connection: The term 'Connect-MsolService' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. "" Aby thoughts on this?
  Expand Post
  - Viktors
    8 years ago
    Please, check 2.1 section of Snow instruction for O365 connector. There are two tools should be installed on the computer, where SIM is configured: Regarding API role - this information also is avalable in prerequisites section. Regards, Viktors
    Expand Post
    Portal User
    8 years ago
    Thank you for the help. I did get this working. I guess I need to slow down and read the instructions (RTFM) a little more thoroughly and in the right order.
    Expand Post
carolai
8 years ago
1. Your Serverconfiguration looks good, although /api is not really required 2. You need to use a user with the role API users. I created a separate user for this in SMACC, gave it only the role "API users", no organisation restriction and set password to "Password never expires". With that user you normally should get the customer DEMO in your O365 connector settings and you can proceed with O365 configuration. Hope this will help you.
Expand Post
mszcz
6 years ago
That is quite old, but I've recently had the same problem and I have solution. There is appendix in guide and that is needed to add exclusion for API folder authentication on SLM website

The Snow License Manager Web API (SLM Web API) uses basic authentication. For the SLM Web
API functionality to work properly, authentication requests need to be passed through to the API
instead of being handled by the IIS (web server). This means that if Windows Authentication is
enabled for the SLM site, an exception allowing anonymous requests must be made for the API in
the SLM web configuration.
Add the following changes in the <configuration> section of the SLM web.config file:
<location path="api">
<system.webServer>
<security>
<authentication>
<anonymousAuthentication enabled="true" />
<basicAuthentication enabled="false" />
<windowsAuthentication enabled="false" />
</authentication>
</security>
</system.webServer>
</location>
Expand Post