Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update AL Home to let partners know about the incoming key vault validation #7986

Open
wants to merge 5 commits into
base: master
Choose a base branch
from
Open

Update AL Home to let partners know about the incoming key vault validation #7986

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
10e2fb8
progress
nndobrev Feb 20, 2025
8c611da
update
nndobrev Feb 25, 2025
426378d
Update news
nndobrev Feb 26, 2025
7d31428
Update News.md
SusanneWindfeldPedersen Feb 26, 2025
981a827
Update News.md
SusanneWindfeldPedersen Feb 26, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions News.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,13 @@
# 2025-02-26 Upcoming changes to the process of how we set up app key vaults for AppSource Apps

We're updating the [process](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/setup-app-key-vault) for registering partner tenants to use the key vault feature in their AppSource apps and moving to a fully automated process in the coming month. For this change to work properly we need to make sure that no partners have specified unused `keyVaultUrls` properties in their `app.json` files. The following concequences should be considered starting **1st of April 2025**:

1. Every AppSource submission with non valid entries in the `keyVaultUrls` property in the `app.json` file, will automatically be picked up for registration. If you don't want to register your key vault, please remove it from your `app.json` file before submitting. Any non valid or forgotten key vault URL will result in a submission failure. For more details follow the guidelines provided in the failure message in Partner Center.
2. Every AppSource submission that contains apps that already have an Entra Tenant ID registered will not fail even if they don't have a `AllowedBusinessCentralAppIds` special secret in their key vault URL. However, we highly recommend adding the secret by following the description in the [guide](https://learn.microsoft.com/dynamics365/business-central/dev-itpro/administration/setup-app-key-vault) to avoid submissions failing in the future.
3. All Azure KeyVault URLs that are valid will result in registering the tenant ID that these key vaults belong to.

Note, that currently the deprecation scenario isn't supported and once the tenant ID is registered to an app, it can't be changed without reaching out to support in Partner Center.

# 2024-10-23 Business Central 2024 release wave 2 launch event content for developers

The Business Central 2024 release wave 2 went live on October 1st and with it the launch event was kicked off with videos on the latest innovations for Business Central. These videos contain high-quality content presented by product leaders to enable you to learn how to take Business Central to the next level as a developer. Visit the [Business Central Youtube channel](https://www.youtube.com/@MicrosoftDynamics365BC) to see what is available. We've produced a lot of content, and we guarantee you that it will be worth the time you invest in it.
Expand Down