EntityFramework.Docs VS IntuneManagement

Each release of Entity Framework Core the Microsoft engineers provide code samples. Although these code samples are great, they are not structured for learning and use in a developer’s projects. Also, there are many code samples that may not be useful to the average developer. With that said I took Microsoft code samples and structured the code in a fashion suitable for the average developer to learn from.

This is documented well for Entity Framework Core, with code samples as well, but there isn't any clear information about having a multi-tenant, multi-db approach for the token cache. The official Multi tenant Azure AD documentation does mention the token caches, but it doesn't talk about a multi-db approach.

Even from the Microsoft example, they use .HasData in their modelbuilder. MicrosoftGithubSeedExample

What have you tried? What doesn't work? The link you provided is a fairly straightforward example of the concept. Including the sample code.

Take a look at this sample project: https://github.com/dotnet/EntityFramework.Docs/tree/main/samples/core/Miscellaneous/Testing/ItemsWebApi/Tests

Micke-K/IntuneManagement: Copy, export, import, delete, document and compare policies and profiles in Intune and Azure with PowerShell script and WPF UI. Import ADMX files and registry settings with ADMX ingestion. View and edit PowerShell script. (github.com)

Export it with Intune Manager "https://github.com/Micke-K/IntuneManagement" I imported my .json configurations with this "$Groups = Get-Content '.\Templates\Groups\CFG_TEST.json' | ConvertFrom-Json" And export again as working .json with "$DeviceConfiguration | ConvertTo-Json -Depth 10 | Out-File -FilePath ".\Output\DeviceConfiguration\Win10" But i needed to create new .json files for every entry in the .csv and not put the whole .csv in the json. But the above way worked for importing/exporting. I hope this helped you a little.