Home Community Uploads

Cireson Partners, Customers and Community members share your customizations and examples here to help benefit the community as a whole to earn Kudos and badges.


All files and projects located here are provided and come "as-is" and without any warranty or support. Use at your own risk. Your use of Community Uploads is subject to our Terms of Use.

Cireson does not and will not support or maintain these enhancements, extensions, and scripts.

For Team Cireson uploads click here.

An SMlets based Exchange Connector



  • Adam_DzyackyAdam_Dzyacky Product Owner Contributor Monkey ✭✭✭✭✭

    Bug fixes + an amazing new feature = v1.8 and v2.2 of the SMLets Exchange Connector out now!

    Predict Configuration Items: Last year Azure Machine Learning was brought into the connector to predict Work Item Type (IR/SR), Support Group, and Classification of a New Work Item. So it only makes sense to follow through and now predict the Impacted Config Item the email is about. This extends the original AML Experiments as it once again is built around you, your organization, and your data. That means regardless if you're using:

    • stock Service Manager (SCSM) classes
    • imported Operations Manager (SCOM) classes
    • Cireson Asset Management
    • ANY 3rd party management packs
    • or even your own in house developed management packs/Config Items for SCSM/SCOM

    The connector can automatically relate the Impacted Config Item on New Incidents or Service Requests. Just like before, all you need to get started is a CSV of Work Items and their Affected Config Items. And of course - the Github wiki has a detailed walk-through alongside all the SQL queries you need to get started. Spare your Analysts the paperwork, improve your reporting and realize Service Manager's true CMDB potential with Machine Learning today!

    A few long standing bugs were addressed in this release as well a few around default Multi-Mailbox functionality (thanks @Ryan_Kennedy1!), visual only bugs when Multi-Mailbox isn't used, and edge cases with the Merge Replies functionality.

    Lastly -

    • I am looking for testers for those running their workflow mailbox in Office 365 to try out OAuth functionality per the steps laid out over here.
    • 1 other feature almost made it into this release, but we'd like some validation from those using the connector first. The ability to submit work on behalf of others using a [for] keyword. Does the proposed implementation work for you? Give a thumbs up, thumbs down, or leave a response on the issue.
    • Willing to help try and repro an issue on Dynamic Analyst Assignment?
    • Are you doing something creative with the connector you think everyone should know about? Reporting? Custom Actions? No process is too small, so let's hear about it!
  • Adam_DzyackyAdam_Dzyacky Product Owner Contributor Monkey ✭✭✭✭✭
    • It understands with Azure Text Analytics
    • It thinks with Azure Machine Learning
    • It sees with Azure Vision
    • It hears and translates with Azure Speech

    It is the most advanced email connector your service desk has ever worked alongside. SMLets Exchange Connector v1.9 and v2.3 are out today!

    Azure Vision: Images attached to emails can now be optionally processed by Azure Vision Services in order to first describe them and assuming text is detected - Optical Character Recognition (OCR) to be used to extract text from them. Now you can turn screenshots of error message into searchable text!

    Azure Speech: *.wav or *.ogg files attached to emails can now be optionally processed by Azure Speech Services to transcribe audio to text. Whether it be voicemails or recordings, audio files in Service Manager can be searched!

    Best of all these new data points are stored inside your Service Manager deployment for use in any number of PowerShell automation and reporting scenarios you can come up with.

    And of course to wrap things up - a few note worthy items:

    • Shout out to first time contributor bennyguk for identifying and fixing a bug around Dynamic Analyst Assignment when used in combination with SCSM Out of Office. Thank you for righting my wrongs and helping everyone in the process!
    • Barring bug related hot-fixes, this marks the last of the v1.x releases. Which means in the near future v2.x will take over as the main branch. I will absolutely keep it (v1.x) around in the repo for long term reference. But if you haven't upgraded yet, now is the time to do so!
    • Microsoft has released Exchange Connector 4.0 with Office 365/OAuth support. As some of you know I've been working on that this year and happy to share that the SMLets Exchange Connector will see this functionality very soon.
    • The Artificial Intelligence project has completed! Well...for now that is 😉
  • Gabriel_LencesGabriel_Lences Customer Advanced IT Monkey ✭✭✭
    edited August 25

    @Adam_Dzyacky d, one could post a long wall of text, but sometimes an image is worth more than countless words.

    (While I don't see us implementing Azure Machine learning stuff anywhere in the near future, the features just sound awesome on paper, so I'm sure it's a real blast in reality! 😊)

  • Mikkel_MadsenMikkel_Madsen Customer Advanced IT Monkey ✭✭✭

    Sorry to say @Adam_Dzyacky but it does not belong in community uploads any longer 🤣🤣🤣

  • Adam_DzyackyAdam_Dzyacky Product Owner Contributor Monkey ✭✭✭✭✭
  • Adam_DzyackyAdam_Dzyacky Product Owner Contributor Monkey ✭✭✭✭✭
    edited September 15

    Psssst. SMLets Exchange Connector v2.4 is out!

    OAuth 2.0 for Exchange Online: If you've been following the Exchange Team's announcements over the last year or so. Basic Authentication's retirement date for Exchange Online has been a bit fluid. Whichever the case - it put the connector in need of newer authentication schemes to ensure those running their mailboxes in 365 continued to function without a hiccup. The functionality is here and with a fully detailed walkthrough on the wiki on how to configure.

    In order to achieve OAuth 2.0 support, the Exchange Web Services DLL now requires the latest version of v2.2 compared to the previous v1.2.

    This release also addressed a tiny visual issue wherein toggling the Use Autodiscover checkbox had no impact on your ability to actually edit the Autodiscover URL textbox.

  • Joakim_NormannJoakim_Normann Customer IT Monkey ✭

    @Adam_Dzyacky in the instructions on https://github.com/AdhocAdam/smletsexchangeconnector/wiki/Configuration-Examples#scenario-3-exchange-onlineoffice-365-with-oauth you mention at the Task Scheduler that we should be using the Microsoft Secrets Management module to store the credentials. To register the password I should run a powershell command as the account running the task. In my specific case, we run the task with the workflow account, but access the mailbox with another account. The credentials for the mailbox is specified in the script. Can I go ahead with the same setup as before or do I need to do anything different in order to get version 2.4.0 to work properly?

  • Adam_DzyackyAdam_Dzyacky Product Owner Contributor Monkey ✭✭✭✭✭
    edited October 23

    So the idea with Secrets Management @Joakim_Normann is that it helps you avoid storing credentials in plain text and instead securely with the credential vault built into Windows.

    So if your Workflow Account is running the script but a different user is a connecting to Exchange in the script - the Workflow Account needs to store those credentials in its cred vault so it can retrieve them when the script runs. Secrets Management (last I checked) stores vaults per user. I mention this only because if you were to store the credentials as your user, the workflow account would have no way to access them. So as far if you need to do anything differently, if you scroll to the bottom of that walkthrough there is a screenshot that highlights how to use in SMA/Azure Automation. These are the same variables you'd update in the script so Task Scheduler and Workflow account could pull the credentials.

    BUT... I should add that Secrets Management is more of a bridge solution to v3.0 of the connector which is currently in its second beta. The new version allows you to securely work with Run as Accounts, the scsm workflow engine, get detailed logging, and do away with Task Scheduler & Secrets Management. The only currently known issue is lack of impersonation support in Exchange.

  • Joakim_NormannJoakim_Normann Customer IT Monkey ✭

    I successfully ran Install-Module -Name "PowerShellGet" -Force and Update-Module -Name "PowerShellGet", but when I tried to run install-module Microsoft.PowerShell.SecretsManagement -AllowPrerelease as suggested in the instructions, I get the message "PackageManagement\Install-Package : No match was found for the specified search criteria and module name 'Microsoft.PowerShell.SecretsManagement'."

  • Adam_DzyackyAdam_Dzyacky Product Owner Contributor Monkey ✭✭✭✭✭

    The message you receive signals that you're unable to talk to the PowerShell Gallery. If you run:


    Do you get any results? If you do not receive any results it means that somewhere along the way, PowerShell lost the config to connect to PSGallery. You can re-register that connection with:

    Register-PSRepository -Default

Sign In or Register to comment.