When I follow the steps above and go to the Samanage app > Provisioning > I only get the Manual mode. How do I get the Automatic mode that this documentation shows I should be able to use?
âš Do not edit this section. It is required for docs.microsoft.com âžź GitHub issue linking.
@bernardw1
Thanks for the feedback! We are currently investigating and will update you shortly.
@bernardw1 Please check if you have all below prerequisites mentioned in the document covered.
An Azure Active directory tenant
A Samanage tenant with the Professional plan or better enabled
A user account in Samanage with Admin permissions
Yes I do have all those prerequisites. That is why I am trying to follow this document. Unfortunately I am not able to follow the steps because azure does not let me select “automatic” provisioning. It only has the option for manual. Do you want a screenshot showing this?
Sent from my Windows 10 phone
From: Mohit Gargnotifications@github.com
Sent: Thursday, March 8, 2018 7:53 PM
To: MicrosoftDocs/azure-docsazure-docs@noreply.github.com
Cc: Bernard Welmersbwelmers@KnutsonConstruction.com; Mentionmention@noreply.github.com
Subject: Re: [MicrosoftDocs/azure-docs] How to set Provisioning Mode (#5496)
@bernardw1https://github.com/bernardw1 Please check if you have all below prerequisiteshttps://docs.microsoft.com/en-us/azure/active-directory/active-directory-saas-samanage-provisioning-tutorial#prerequisites mentioned in the document covered.
An Azure Active directory tenant
A Samanage tenant with the Professional plan or better enabled
A user account in Samanage with Admin permissions
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/5496#issuecomment-371687302, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AWPSuszYADu97xlUprbQxQldfvqwoR4Fks5tceCUgaJpZM4SjdXv.
Please open this case again. It is really annoying that you closed it without actually looking at the issue I was having or giving me a chance to reply to your post.
here is an image of the issue that I am having.
@bernardw1 Apologies that issue was closed without your confirmation. I have reopened this issue so that we continue the discussion here and capture all details in this thread itself. Please let me know if this is fine with you. Let me know if you are fine closing the other issue.
Please note that Samanage tenant by default is not professional. I was able to repro it when we choose Samanage application from Enterprise application list from gallery. However, if you have purchased professional plan you must not face this issue. Please confirm on it.
@asmalser-MSFT Also I am assigning this to you to confirm if above information provided is correct. Please add additional details if necessary.
Yes I am happy to discuss the issue in this thread, and you can close the other thread, I just wanted to make sure that the topic was seen since this one was marked as closed.
As to our plan with Samanage, we do have the professional plan with Samanage. It is currently a trial but we are purchasing the professional plan with them. Here is a screen shot showing that we have the professional plan.
So to combine some of the information in the other thread here.
We do have Office 365 and the associated Azure Tenant.
I do have Samanage SSO working with Azure SAML2.0
I do have Samanage Professional
The issue with the documentation is that when I follow the steps I am unable to complete step 4- Set the Provisioning Mode to Automatic. Unfortunately this is not an option for me in enterprise application in Azure. (screen shot of this is attached above).
Has a solution been found to this yet? I'm having almost identical situation, all prerequisites met as well but nothing more than 'Manual' option for Provisioning. Any update is appreciated.
@asmalser-msft Please update on above.
Our organization has the exact same issue as @bernardw1. The "automatic" option is missing in the Provisioning Mode drop down.
We are also running on a professional plan for Samanage.
Bueller?
Any update on this? We are having the same issue.
Problem acknowledged, There is an issue with the connector not being fully published in the Azure portal. A fix is coming very soon. Sorry for the inconvenience.
@MicrosoftDocs/azure-cxp-triage This is an acknowledge product issue. Please remove the "doc bug" label.
Thank you for acknowledging that there is an issue with the connector. I hope it comes soon it will be VERY useful to have.
Just so everyone on this thread knows, the automatic provisioning feature has not worked since the article was originally published last year. I got a response from a Microsoft employee "Jeevan Desarda" on the old Livefyre commenting system who told me it would be working by the end of January but that never happened. Now that the article has disappeared from Microsoft's site altogether, I think this feature may be dead in the water. One of the many reasons we are already considering dumping Samanage just 2 years in.
We are also looking to utilize the Azure AD Samanage app for both authentication and provisioning. From what I understand, Microsoft needs to fix the provisioning side of the published Samanage app. I'm told it didn't work due to a bug and was pulled but no fix was ever posted.
Can anyone at Microsoft please let me know when this might be made available? I can't imagine it would be that difficult. I know that OneLogin currently works for both authentication and provisioning proving it's entirely possible but we would like to leverage Azure AD.
This is a priority for us. Any update on the status of this would be much appreciated. Thanks!
@tysonmock / @Mabunga / @bernardw1 I am checking internally on what's the progress on this and will share what i can find.
@tysonmock / @Mabunga / @bernardw1 So here's what is going on, hopefully it will clarify things. A mix-up caused the documentation to go live before we were ready with the connector, an update for the documentation and connector is in the works and the release is imminent. I will update here once it goes live.
Thanks for the update! hopefully it happens soon, many of us will be glad for the automated system.
@amanarneja Do you have an update on when we could expect this? We are currently implementing Samanage and want to get a feel for what "imminent" means in this context. We'd like to avoid having to manually provision all of our accounts if we can avoid it. Thank you!
Thanks for sharing some situational insight Aman...many of us are patiently awaiting Microsoft's official release of this connector and do hope it arrives soon
@tysonmock / @jmbradd Following up with the team building the connector. Will get back to you as soon as i hear again, when i discussed with them last week the _imminence of "imminent" was quite imminent_ :) apologies for the delays will update here as soon as i learn more.
We're very close to a fix and making the documentation live again. We acknowledge there have been problems in the last several months with the documentation being published prematurely, and then with finally getting this enabled for everyone in the Azure portal. The connector is done. At this point we are just working through some issues in the publishing process.
Update: The publishing issue has been resolved, and the connector and documentation are expected to go live next week. Thanks everyone for your patience! #please-close
@asmalser-msft - Thank you very much for getting that republished. It looks like it will work really nicely.
I do have a couple questions - Is there going to be any documentation on how to setup the provisioning? I think I have gotten it figured out but Just wanted to ask.
(I would post this to the "application" github comment area but I don't know how to get there).
Also instead of User Name and Password - how hard would it be to change that or add the ability to use a Token instead? Samanage makes it really easy to generate an authentication token that is tied to the the administrator account that is making the API calls. This would allow the account to be used even if the password is changed.
From the Samange API documentation ::
In order to supply the API token you should pass X-Samanage-Authorization header in the following format: “Bearer API_TOKEN_STRING”. Assuming that the token obtained in the user setup page is AAAZWV0YXkubmF0YW4rNUBzYW1hbmFnZS5jb20hbGciOiJIUzUxMiJ9.eyJ1c2VyX2ljIjoxMjU2OTQzLCJnZW5lcmF0ZWRfYXQiOiIyMDE3LTA2LTA3IDA5OjE3OjI5In0.j_H15qzJJr9vXGAHCThLEOQrE9GGbjMxZJOs5zAf_iqaGqxlIOAmvPpBx0td_C3r7dliAfXXIgdqhZHVoK1KTwAzd1 the API call looks like this:
Example:
curl -H "X-Samanage-Authorization: Bearer AAAZWV0YXkubmF0YW4rNUBzYW1hbmFnZS5jb20hbGciOiJIUzUxMiJ9.eyJ1c2VyX2ljIjoxMjU2OTQzLCJnZW5lcmF0ZWRfYXQiOiIyMDE3LTA2LTA3IDA5OjE3OjI5In0.j_H15qzJJr9vXGAHCThLEOQrE9GGbjMxZJOs5zAf_iqaGqxlIOAmvPpBx0td_C3r7dliAfXXIgdqhZHVoK1KTwAzd1" -H "Accept: application/vnd.samanage.v2.1+xml" https://api.samanage.com/hardwares.xml
Hi, Was the documentation for this connector ever made live? I am trying to get the user provisioning with Samanage to work correctly but I am running into errors and I cannot find any documentation to reference. Thanks!
I have tried every way I could think of and was unable to get it to work. As result I think t has not been fully vetted. And I have not seen any documentation either.
Sent from my Windows 10 phone
From: jagee23notifications@github.com
Sent: Tuesday, June 19, 2018 4:39 PM
To: MicrosoftDocs/azure-docsazure-docs@noreply.github.com
Cc: Bernard Welmersbwelmers@KnutsonConstruction.com; Mentionmention@noreply.github.com
Subject: Re: [MicrosoftDocs/azure-docs] How to set Provisioning Mode (#5496)
Hi, Was the documentation for this connector ever made live? I am trying to get the user provisioning with Samanage to work correctly but I am running into errors and I cannot find any documentation to reference. Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_MicrosoftDocs_azure-2Ddocs_issues_5496-23issuecomment-2D398555059&d=DwMCaQ&c=n7L0v4WPJp8RJ0c-Bej7fEGm_YfMKuaC1CFAEEbR5T0&r=Ws-uW3BOwovMmvyBUuSZoo_g6X-gMyNW71HadNGI7oE&m=RpvLtCMs3ONSnDb6O78mo3dyCnGrCvJkk4BSYt1WXCU&s=YfhbMNc7paZ_ZtFwjXIoMtwVxovPbk9PZ-vlQ2DLEzA&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AWPSugNaKUzUTzTRiV-5FA7H-2DeqiBmQ11-2Dks5t-2DW-2DhgaJpZM4SjdXv&d=DwMCaQ&c=n7L0v4WPJp8RJ0c-Bej7fEGm_YfMKuaC1CFAEEbR5T0&r=Ws-uW3BOwovMmvyBUuSZoo_g6X-gMyNW71HadNGI7oE&m=RpvLtCMs3ONSnDb6O78mo3dyCnGrCvJkk4BSYt1WXCU&s=FK0xKj2jfZ1KqpSL15NEaOgOUYNyDKWSAN-N8bGnoLc&e=.
Most helpful comment
Yes I am happy to discuss the issue in this thread, and you can close the other thread, I just wanted to make sure that the topic was seen since this one was marked as closed.
As to our plan with Samanage, we do have the professional plan with Samanage. It is currently a trial but we are purchasing the professional plan with them. Here is a screen shot showing that we have the professional plan.
So to combine some of the information in the other thread here.
We do have Office 365 and the associated Azure Tenant.
I do have Samanage SSO working with Azure SAML2.0
I do have Samanage Professional
The issue with the documentation is that when I follow the steps I am unable to complete step 4- Set the Provisioning Mode to Automatic. Unfortunately this is not an option for me in enterprise application in Azure. (screen shot of this is attached above).