Windows-itpro-docs: Dead Link for JPN translation document

Created on 4 Mar 2019  ·  12Comments  ·  Source: MicrosoftDocs/windows-itpro-docs

The URL assigned in [Azure PowerShell コマンドレットを使用して、Virtual Machines および Cloud Services 向けの Microsoft マルウェア対策] is in Dead Link.
Please fix URL if possible.


ドキュメントの詳細

このセクションを編集しないでください。 docs.microsoft.com で必須です ➟ GitHub の問題のリンク。

Most helpful comment

@illfated you are right, there is a private branch that no-one works in (most people don't even know it is there) -the public and private repos are automatically synced but the repo admins have to merge from master to live through this extra layer because it was set up that way .(as I understand it)) About the links, I will get back to you after doing some research. :smile:

All 12 comments

@OfficeGlobal

@mypil It's the source issue, the link "Microsoft Antimalware for Virtual Machines and Cloud Services with Azure PowerShell cmdlets" is not available in source article https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-antivirus/deploy-manage-report-windows-defender-antivirus#fn3

@andreabichsel - the URL for the source article (https://github.com/MicrosoftDocs/windows-itpro-docs/blob/live/windows/security/threat-protection/windows-defender-antivirus/deploy-manage-report-windows-defender-antivirus.md) is getting a 404 error. Can you please advise on how this can be fixed?

cc: @kenwith @AndreaBarr

@andreabichsel - I would like to follow up on this issue. Do you happen to know the correct URL for the source article? Please advise so we can create a PR to get this fixed. Thank you.

@illfated - I'm not sure about that. Tagging @andreabichsel and @kenwith as they might know the answer and have some information.

My guess is that the link with "/live/" in it might be for localized content. I don't use that branch at all.

Fair enough, not a big deal, except for the conundrum of why the Japanese page used the /live/ branch link
in the opening issue comment, instead of the /master/ branch link.

From my point of view, the focus needs to be on where the correct documentation is located.
Maybe in one of the other repositories, like Azure or PowerShell?

https://github.com/MicrosoftDocs/azure-docs-powershell/blob/master/azuresmps-4.0.0/Azure/Azure.md

https://docs.microsoft.com/powershell/module/servicemanagement/azure/set-azurevmmicrosoftantimalwareextension?view=azuresmps-4.0.0

I am uncertain how to continue from here, because the documentation in the originating page seems to indicate that the linked page with PowerShell cmdlets should list both Virtual Machines and Cloud Services cmdlets on the same page.

Also, there is the original link structure to consider, is the likeness in a new link of any importance?
(thinking aloud, so to speak - if missing text could have played any role in the original link)

Overview: https://docs.microsoft.com/en-us/azure/security/azure-security-antimalware
new_link1: https://github.com/MicrosoftDocs/azure-docs-powershell/blob/master/azuresmps-4.0.0/Azure/Get-AzureVMMicrosoftAntimalwareExtension.md
new_link2: https://github.com/MicrosoftDocs/azure-docs-powershell/blob/master/azuresmps-4.0.0/Azure/Get-AzureServiceAntimalwareConfig.md

dead link: https://docs.microsoft.com/powershell/servicemanagement/azure.antimalware/v3.4.0/azure.antimalware

@officedocsbot assign @mypil

@illfated you are right, there is a private branch that no-one works in (most people don't even know it is there) -the public and private repos are automatically synced but the repo admins have to merge from master to live through this extra layer because it was set up that way .(as I understand it)) About the links, I will get back to you after doing some research. :smile:

Was this page helpful?
0 / 5 - 0 ratings

Related issues

KamilSzafarczyk picture KamilSzafarczyk  ·  3Comments

illfated picture illfated  ·  3Comments

michalzobec picture michalzobec  ·  3Comments

RAJU2529 picture RAJU2529  ·  3Comments

ang216 picture ang216  ·  3Comments