web
You’re offline. This is a read only version of the page.
close
  • LCS integration with own custom VSTS templates

    Customers want to leverage Visual team services and want to change the standard vsts project template to add their own status. Now you get an error in LCS when you want to add for example a custom status of a task. "internal test done". It is better to have the posiblility to add status and modify the template more and make it possible to map your custom template with life cycle services so that customers can work in LCS and VSTS and hold and track in one system all statussen about the tasks, user stories and bug .

  • add the right contacts of an LCS project to an support case and the contact order

    In LCS you should do administrative tasks with an admin account. That should not be used for day to day use the idea is that you create a case and that in the contact section of the support case you should be able to select the project users from lcs and add thier role and contact order so that the Microsoft support can see that the task is done by the administrative account and can contact the right people in the right order if the fist person is not reachable

  • ICP TaxEvatParameters_NL

    The current TaxEvatParameters_NL solution in Dynamics 365 for Finance and Operations is reflecting the way it should be implemeted acording to logius (https://logius.nl/diensten/digipoort) customer because you must first test the communication from the envirionment they are sending the ICP declaration. Currently the documenation is also incorrect https://docs.microsoft.com/en-us/dynamics365/unified-operations/financials/localizations/tasks/nl-00010-electronic-tax-declarations-evat I have added the information I got from Logius. I have contact Microsoft support and asked me to post this on ideas. Currently the ICP onboarding is not supported with Dynamics 365 for Finance and Operations and when you want to test ICP in production you can not remove the posting. So test needs to be implemented so that on certificate change the customer can retest if everything is working correctly. connect Suite • https://cs-bedrijven.procesinfrastructuur.nl/cpl/aanleverservice/1.2 • https://cs-bedrijven.procesinfrastructuur.nl/cpl/statusinformatieservice/1.2 • https://cs-bedrijven.procesinfrastructuur.nl/cpl/machtigingraadpleegservice/services/MachtigingRaadpleegService_V1_2 • https://cs-bedrijven.procesinfrastructuur.nl/cpl/ophaalservice/services/OphaalService_V1_2 PreProduction Logius uses the PreProduction environment for the further development of Digipoort. With some streams, the environment is also used for chain testing. This option is not offered for the Tax Authorities flows. • https://preprod-dgp.procesinfrastructuur.nl/wus/2.0/aanleverservice/1.2 • https://preprod-dgp.procesinfrastructuur.nl/wus/2.0/statusinformatieservice/1.2 • https://preprod-dgp.procesinfrastructuur.nl/wus/2.0/ophaalservice/1.2 • https://preprod-dgp.procesinfrastructuur.nl/wus/2.0/machtigingraadpleegservice/1.2 New preproduction endpoints related to TLS1.2 + Certificate exchange 2017 * • https://preprod-dgp2.procesinfrastructuur.nl/wus/2.0/aanleverservice/1.2 • https://preprod-dgp2.procesinfrastructuur.nl/wus/2.0/statusinformatieservice/1.2 • https://preprod-dgp2.procesinfrastructuur.nl/wus/2.0/ophaalservice/1.2 • https://preprod-dgp2.procesinfrastructuur.nl/wus/2.0/machtigingraadpleegservice/1.2 Producton • https://dgp.procesinfrastructuur.nl/wus/2.0/aanleverservice/1.2 • https://dgp.procesinfrastructuur.nl/wus/2.0/statusinformatieservice/1.2 • https://dgp.procesinfrastructuur.nl/wus/2.0/ophaalservice/1.2 • https://dgp.procesinfrastructuur.nl/wus/2.0/machtigingraadpleegservice/1.2(This endpoint cannot be accessed via the browser. Messages sent to this endpoint are processed correctly.) New production endpoints related to TLS1.2 + Certificate exchange 2017 * • https://dgp2.procesinfrastructuur.nl/wus/2.0/aanleverservice/1.2 • https://dgp2.procesinfrastructuur.nl/wus/2.0/statusinformatieservice/1.2 • https://dgp2.procesinfrastructuur.nl/wus/2.0/ophaalservice/1.2 • https://dgp2.procesinfrastructuur.nl/wus/2.0/machtigingraadpleegservice/1.2(This endpoint cannot be accessed via the browser. Messages sent to this endpoint are processed correctly.)
  • Cleanup Deployable package directory after succesfull deployment

    To clean up the deployable package directory to avoid, running out of diskspace. Or a cleanup job that runs every 2 weeks. This job you should be able to execute from LCS portal.
  • upload the same assets in the global asset library for the ch. eu. fr tenants

    Currently in the eu.lcs and fr.lcs, ch.lcs, no.lcs the nuget packages are not available. Can this be resolved that all the packages are automaticality uploaded to the local lcs tenants so that customer who does not want to uses services in the USA can also download the packages from the local lcs.



  • Managed identity support for deployment with Dynamics 365 Unified operations and Life cycle service for all lcs geo's

    A common challenge for developers is the management of secrets, credentials, certificates, and keys used to secure communication between services. Managed identities eliminate the need for developers to manage these credentials. And to avoid creating dedicated service account for authentication in Azure DevOps or LCS is not a good partice since it is difficult to update and maintain the password change and block login when a service account is compromised. And if you read the https://learn.microsoft.com/en-us/microsoft-365/troubleshoot/sign-In/determine-account-is-compromised article for service account that are used to authenticate in Azure DevOps for example support and also if a partner want to support the scenario you have the issue that you can face and is very common nowadays. double multi-factor authentication. see chapter below And you have to execute the account which is a risk.





    Possible double multi-factor authentication


    With Azure AD B2B, you can enforce multi-factor authentication at the resource organization (the inviting organization). The reasons for this approach are detailed in Conditional Access for B2B collaboration users. If a partner already has multi-factor authentication set up and enforced, their users might have to perform the authentication once in their home organization and then again in yours.


    found on

    https://learn.microsoft.com/en-us/azure/active-directory/external-identities/current-limitations#possible-double-multi-factor-authentication


    hope more people that are looking for a higher level of security and functionality of the Microsoft Dynamics 365 Finance and Operations stack, Azure DevOps and Life Cycle Service in all the Geo's


    Thanks in advance for putting this on the roadmap