Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2023 Release Wave 1Check out the latest updates and new features of Dynamics 365 released from April 2023 through September 2023
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I have a legacy application connected to cloud d365 that uses:
XrmServiceContext : Microsoft.Xrm.Client.CrmOrganizationServiceContext
from Microsoft.Xrm.Client namespace. It was downloaded from there back then. The connetion string looks like this:
is the code affected by WS-Trust deprecation announced by MSFT?
YES.This is the exact example you have on Use of Office365 authentication with Microsoft Dataverse (Microsoft Dataverse) - Power Apps | Microsoft Docs. On the same link, you have the documentation on how to fix this: basically change the ConnectionString and the code used to point to the new OrganizationServiceProxy class.
Please note that the SDK package you've donwloaded is/was valid for v8.x organizations (CRM 2016 onPremise). If you're still using this (onPremise software) you might continue to use your old code. Otherwise, if using onPrem v9 or Dynamics 365 Online, you should use the new version (v9) of the SDK available on https://docs.microsoft.com/dynamics365/customer-engagement/developer/download-dynamics-365-sdk-v9
Business Applications communities