text:
SAML Question - B2C as IdP

Hi, we're trying to use AWS Cognito user pool as SP and Azure AD B2C as IdP. Unfortunately, we haven't had any success yet. The SAML request is failing. The SAML response from Azure B2C has the following status message, indicating the RelayState content from AWS Cognito is too big (> 1000 byte max):
<samlp:Status>
      <samlp:StatusCode Value="urn:oasis:names:tc:SAML:2.0:status:Requester" />
      <samlp:StatusMessage>The SAML RelayState content is greater the 1000 bytes.</samlp:StatusMessage>
      <IsPolicySpecificError>false</IsPolicySpecificError>
</samlp:Status>

After decoding the RelayState (2x base64), we see this (some sensitive names changed to abc's):
{"userPoolId":"us-east-1_Vu6ccYQri","providerName":"ABCD-B2C-TEST","clientId":"s1ldupjg52rk4vrrumab75nq0","redirectURI":"abcdefghij://abcdefghij.abc.com/authmain","responseType":"code","providerType":"SAML","scopes":["aws.cognito.signin.user.admin","email","openid","phone","profile"],"state":null,"codeChallenge":null,"codeChallengeMethod":null,"nonce":"DDKMFvrQXZl1ML2Fg9pPTRVamRmx06_nWNSNV5wDsFp6-Nl4OcM2FixoNg5FHoIJ7LlT4tByiSE7-2NqeFhLhx_n7y-m_e6BQnBYFWwYdQr7LUMUj9HJDMLds1rkxP4ttwXPFMv4Yq5gpRnSkoW0jeZ1hkMIvqGZyNo8X82PZkA","serverHostPort":"abcdefghijklmnopqrs.auth.us-east-1.amazoncognito.com","creationTimeSeconds":1583530949,"session":null,"userAttributes":null,"isStateForLinkingSession":false}

We tried to shrink the size with everything we can control, but the smallest we could get is still too big after encoding it. The cryptographic nonce is the biggest part, but we can't control that.
Is there a way to configure B2C to allow a larger RelayState coming from AWS Cognito? Or any other suggestions on how to deal with this problem?
I opened this in docs due to the links on this page -- https://docs.microsoft.com/en-us/azure/active-directory-b2c/connect-with-saml-service-providers
However, please let me know if I should open it elsewhere.
Thanks!

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1376f79b-474f-4b83-2583-07acd2eeb2f4
Version Independent ID: 45d314dd-c9fa-50a5-cb39-d34db80c7874
Content: Configure Azure AD B2C as a SAML IdP to your applications
Content Source: articles/active-directory-b2c/connect-with-saml-service-providers.md
Service: active-directory
Sub-service: b2c
GitHub Login: @msmimart
Microsoft Alias: mimart

@doc-rj-celltrak Thanks for your feedback! We will investigate and update as appropriate.

@doc-rj-celltrak Please try adding <Item Key="RequestContextMaximumLengthInBytes">2000</Item>  to your RP file as highlighted below:

Hi @amanmcse we still see the same error after making that change. Do you have any other suggestions? Thanks!

@doc-rj-celltrak Try capturing a fiddler or browser network trace to see the content length of the request and set the value of RequestContextMaximumLengthInBytes accordingly. I am suspecting that request length is more than 2000 bytes due to which you are still getting this error.

Please post this on Stack Overflow and tag the question azure-ad-b2c.
It is also worth noting that the SAML specification mandates that the relaystate must be no larger than 80 bytes. See http://docs.oasis-open.org/security/saml/v2.0/saml-bindings-2.0-os.pdf section 3.4.3

Hi @amanmcse thanks again for your help. I count 1832 bytes after adding together both query params SAMLRequest and RelayState in url-decoded form, 1917 bytes in url-encoded form.
However, just to make sure, I'm going to try to configure the RequestContextMaximumLengthInBytes to 3000 bytes or larger.
Here's the entire request url in url-encoded form:
https://consumerdirectb2ctest.b2clogin.com/consumerdirectb2ctest.onmicrosoft.com/B2C_1A_signup_signin_saml/samlp/sso/login?SAMLRequest=fVJLa9wwEL73VxjdZVvq7qYWa4dtQiCQHJoXtBcjy%2FJGxJIczTik%2FfWVtZvQQMlpkPhezDfb01c7%0AZi86gPGuJiwvSaad8r1x%2B5rc313Qb%2BS0%2BbIFaUc%2Bid2Mj%2B5GP88aMNsB6ICRd%2BYdzFaHWx1ejNL3%0AN1c1eUScQBSF0uOIQT5Z35lRY%2BTxXEaVfAaqJSBlubTyj4%2Bee2fQ58rbIrkVpp%2BChimKa5KdR6Zx%0AElPMd%2FGjcW%2BCVthxtejncY5%2Bb1yS%2Bj%2FEO2tU8OAHTKjv%2FKxluxbM3s1TGsa1S4oUZSoAfJE0SXZ5%0AXpN2XTHdD8OaKlZVdDVsVrTrKkb5ZjXwNV%2BfVF0foQCzvnSA0mFNeMlLWn6ljN%2BVXLBKlDw%2F4ewX%0AyR7e1s%2BX9cdCHIjDwmsyBye8BAPCSatBoBK3u%2BsrEaFiCh698iNpDv2IZBiyCx%2BsxM%2B5y4%2Fp6ZCg%0AQjs0%2BPuD9%2Bd0%2BdY9aRbYoUJx7FDAJN7rbR%2FmjVI%2FfwSzLf5N2RyfH4%2Bq%2BQs%3D&RelayState=ZXlKMWMyVnlVRzl2YkVsa0lqb2lkWE10WldGemRDMHhYMVoxTm1OaldWRnlhU0lzSW5CeWIzWnBaR1Z5VG1GdFpTSTZJa05FUTA0dFFqSkRMVlJGVTFRaUxDSmpiR2xsYm5SSlpDSTZJbk14YkdSMWNHcG5OVEp5YXpSMmNuSjFiV0ZpTnpWdWNUQWlMQ0p5WldScGNtVmpkRlZTU1NJNkltTmxiR3gwY21GcmMyUTZMeTlqWld4c2RISmhhM05rTG1OMGRDNWpiMjB2WVhWMGFHMWhhVzRpTENKeVpYTndiMjV6WlZSNWNHVWlPaUpqYjJSbElpd2ljSEp2ZG1sa1pYSlVlWEJsSWpvaVUwRk5UQ0lzSW5OamIzQmxjeUk2V3lKaGQzTXVZMjluYm1sMGJ5NXphV2R1YVc0dWRYTmxjaTVoWkcxcGJpSXNJbVZ0WVdsc0lpd2liM0JsYm1sa0lpd2ljR2h2Ym1VaUxDSndjbTltYVd4bElsMHNJbk4wWVhSbElqcHVkV3hzTENKamIyUmxRMmhoYkd4bGJtZGxJanB1ZFd4c0xDSmpiMlJsUTJoaGJHeGxibWRsVFdWMGFHOWtJanB1ZFd4c0xDSnViMjVqWlNJNkluaFNURTFsWjJwUlVrZFdjVVJyY2pkWVZqWnZlbTFaU0hOZlJqRXRjRXBTTm5WQlZqTjFlVmQzZFZVdGFsRTRlbDh5TkVkWlZGbG1iR1ZQYVhWR01sZEtWRWhPYnpOeVZFeEVkVzgwV2pWWFMzSXhSSE5VU0dabWFGVXROa0pQVkZaYVkzY3RkbUpCU1d0U2JqWkRSMko0WDB0cExWb3pOazFyYVVSM2FrbFpTMU5sVERKaVVIUnNlbFl0TVRkUmFUUjFaVTlFY1RSV1drMVdiVUZwVW1sb2QxZzJlR2RxVVc0eFl5SXNJbk5sY25abGNraHZjM1JRYjNKMElqb2lZMlZzYkhSeVlXdHRiMkpwYkdWMFpYTjBNaTVoZFhSb0xuVnpMV1ZoYzNRdE1TNWhiV0Y2YjI1amIyZHVhWFJ2TG1OdmJTSXNJbU55WldGMGFXOXVWR2x0WlZObFkyOXVaSE1pT2pFMU9ETTVOemsxTkRJc0luTmxjM05wYjI0aU9tNTFiR3dzSW5WelpYSkJkSFJ5YVdKMWRHVnpJanB1ZFd4c0xDSnBjMU4wWVhSbFJtOXlUR2x1YTJsdVoxTmxjM05wYjI0aU9tWmhiSE5sZlE9PTo5ZEVJYitYSTFOYnNhS09BMXJiaVI0enlkNzlUc3VpTGVRdzUwV2U1SnJBPToz

@WhippsP Thank you, I'll try posting on Stack Overflow, but I'll probably need support from Amazon or Microsoft or both. Regarding the 80 bytes, my understanding is that spec is not followed in actual industry practice. Microsoft apparently defaults to a 1000 byte max, and Amazon specifically says this: "Cognito supports relayState values larger than 80 bytes. Whilst SAML specifications state that the relayState value 'MUST NOT exceed 80 bytes in length', current industry practice often deviates from this behavior. As a consequence, rejecting relayState more than 80 bytes will break many standard SAML provider integrations." Reference here.

@doc-rj-celltrak Have you had a chance to set RequestContextMaximumLengthInBytes to 3000 bytes or larger? If it still fails, please email a fiddler capture of the problem to azCommunity[at]microsoft[dot]com. Also, share the link to your StackOverflow post to this thread as well.
I am proceeding with closure of this thread and will continue to work with you over email and the StackOverflow post.

@amanmcse We will be able to test again when the customer updates their RP file, and I will send an email if it fails. Thank you for your help. The StackOverflow post is here - https://stackoverflow.com/questions/60647109/azure-ad-b2c-as-saml-idp-relaystate-too-big

authors: SaurabhSharma-MSFT WhippsP amanmcse doc-rj-celltrak


text:
I believe this sample should include an expression to check if the location field is present

Team, based on experience this policy is used many times as the base for geo-restricting policies. However, not all resource types require the location field. Resources that don't use the location field will not send them, causing this policy to block all of those resources. Could we add to the policy an extra condition to first check if the location exists before enforcing its value? This should be fine if users do not specify location on resources that do require it as it would return a validation error anyway.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: cc7205c9-e142-3019-39cb-6cde0ffe8baf
Version Independent ID: 471f9317-cb57-7565-c593-3c30413fdf99
Content: Pattern: Field properties in a policy definition - Azure Policy
Content Source: articles/governance/policy/samples/pattern-fields.md
Service: azure-policy
GitHub Login: @DCtheGeek
Microsoft Alias: dacoulte

Thanks for your comment. The feedback has been shared with the content owner for further review. Thanks for your patience.

@milope Thanks for the question! I'm validating with the team that the resource types that don't require a location field are covered by the inclusion of 'global' as a check. As a note, this is a pattern explanation, not a sample. For samples, we recommend looking at the Azure Policy built-ins repo and the Community Policy Repo.
@MicrosoftDocs/azure-cxp-triage #in-progress

@milope Thanks again for asking on this. The pattern is good as-is and only evaluates resource types that have a location by setting "mode": "Indexed". Please make sure that if you are doing a location based policy, that you are setting mode to indexed and it's not set to all.  This is likely the cause of the issue you are seeing. For more information on mode, see Policy definition - mode.  Thanks again!
@MicrosoftDocs/azure-cxp-triage #please-close

source: gharchive/issue

authors: DCtheGeek femsulu milope

repo: MicrosoftDocs/azure-docs

license_type: permissive

license_source: github-api


text:
Page contract selfasserted 2.0.0 seems to break locatisation of built-in strings

This works (page contract 1.2.0):
<DataUri>urn:com:microsoft:aad:b2c:elements:contract:selfasserted:1.2.0</DataUri>

    <ContentDefinitions>
      <ContentDefinition Id="api.selfasserted">
        <LoadUri>https://example.com/unified?ui_locales={Culture:LanguageName}</LoadUri>
        <RecoveryUri>~/common/default_page_error.html</RecoveryUri>
        <DataUri>urn:com:microsoft:aad:b2c:elements:contract:selfasserted:1.2.0</DataUri>
        <Metadata>
          <Item Key="DisplayName">Collect information from user page</Item>
        </Metadata>
        <LocalizedResourcesReferences MergeBehavior="Prepend">
          <LocalizedResourcesReference Language="en" LocalizedResourcesReferenceId="api.selfasserted.en" />
          <LocalizedResourcesReference Language="nl" LocalizedResourcesReferenceId="api.selfasserted.nl" />
        </LocalizedResourcesReferences>
      </ContentDefinition>
    </ContentDefinitions>

    <Localization Enabled="true">
      <SupportedLanguages DefaultLanguage="en" MergeBehavior="ReplaceAll">
        <SupportedLanguage>en</SupportedLanguage>
        <SupportedLanguage>nl</SupportedLanguage>
      </SupportedLanguages>
      <LocalizedResources Id="api.selfasserted.en">
        <LocalizedStrings>
          <LocalizedString ElementType="ClaimType" ElementId="signInName" StringId="DisplayName">Email</LocalizedString>
        </LocalizedStrings>
      </LocalizedResources>
      <LocalizedResources Id="api.selfasserted.nl">
        <LocalizedStrings>
          <LocalizedString ElementType="ClaimType" ElementId="signInName" StringId="DisplayName">E-mailadres</LocalizedString>
        </LocalizedStrings>
      </LocalizedResources>
    </Localization>

This doesn't work (with page contract 2.0.0, built-in strings, e.g. the "Continue" button are not translated):
<DataUri>urn:com:microsoft:aad:b2c:elements:contract:selfasserted:2.0.0</DataUri>

    <ContentDefinitions>
      <ContentDefinition Id="api.selfasserted">
        <LoadUri>https://example.com/unified?ui_locales={Culture:LanguageName}</LoadUri>
        <RecoveryUri>~/common/default_page_error.html</RecoveryUri>
        <DataUri>urn:com:microsoft:aad:b2c:elements:contract:selfasserted:2.0.0</DataUri>
        <Metadata>
          <Item Key="DisplayName">Collect information from user page</Item>
        </Metadata>
        <LocalizedResourcesReferences MergeBehavior="Prepend">
          <LocalizedResourcesReference Language="en" LocalizedResourcesReferenceId="api.selfasserted.en" />
          <LocalizedResourcesReference Language="nl" LocalizedResourcesReferenceId="api.selfasserted.nl" />
        </LocalizedResourcesReferences>
      </ContentDefinition>
    </ContentDefinitions>

    <Localization Enabled="true">
      <SupportedLanguages DefaultLanguage="en" MergeBehavior="ReplaceAll">
        <SupportedLanguage>en</SupportedLanguage>
        <SupportedLanguage>nl</SupportedLanguage>
      </SupportedLanguages>
      <LocalizedResources Id="api.selfasserted.en">
        <LocalizedStrings>
          <LocalizedString ElementType="ClaimType" ElementId="signInName" StringId="DisplayName">Email</LocalizedString>
        </LocalizedStrings>
      </LocalizedResources>
      <LocalizedResources Id="api.selfasserted.nl">
        <LocalizedStrings>
          <LocalizedString ElementType="ClaimType" ElementId="signInName" StringId="DisplayName">E-mailadres</LocalizedString>
        </LocalizedStrings>
      </LocalizedResources>
    </Localization>

This workaround also works (specifying the built in strings, not only the custom ones), but would be annoying to do for all built-in strings:
<DataUri>urn:com:microsoft:aad:b2c:elements:contract:selfasserted:2.0.0</DataUri>

<LocalizedString ElementType="UxElement" StringId="button_continue">Doorgaan</LocalizedString>

    <ContentDefinitions>
      <ContentDefinition Id="api.selfasserted">
        <LoadUri>https://example.com/unified?ui_locales={Culture:LanguageName}</LoadUri>
        <RecoveryUri>~/common/default_page_error.html</RecoveryUri>
        <DataUri>urn:com:microsoft:aad:b2c:elements:contract:selfasserted:2.0.0</DataUri>
        <Metadata>
          <Item Key="DisplayName">Collect information from user page</Item>
        </Metadata>
        <LocalizedResourcesReferences MergeBehavior="Prepend">
          <LocalizedResourcesReference Language="en" LocalizedResourcesReferenceId="api.selfasserted.en" />
          <LocalizedResourcesReference Language="nl" LocalizedResourcesReferenceId="api.selfasserted.nl" />
        </LocalizedResourcesReferences>
      </ContentDefinition>
    </ContentDefinitions>

    <Localization Enabled="true">
      <SupportedLanguages DefaultLanguage="en" MergeBehavior="ReplaceAll">
        <SupportedLanguage>en</SupportedLanguage>
        <SupportedLanguage>nl</SupportedLanguage>
      </SupportedLanguages>
      <LocalizedResources Id="api.selfasserted.en">
        <LocalizedStrings>
          <LocalizedString ElementType="ClaimType" ElementId="signInName" StringId="DisplayName">Email</LocalizedString>
        </LocalizedStrings>
      </LocalizedResources>
      <LocalizedResources Id="api.selfasserted.nl">
        <LocalizedStrings>
          <LocalizedString ElementType="ClaimType" ElementId="signInName" StringId="DisplayName">E-mailadres</LocalizedString>
          <LocalizedString ElementType="UxElement" StringId="button_continue">Doorgaan</LocalizedString>
        </LocalizedStrings>
      </LocalizedResources>
    </Localization>

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c4272fbd-ad3d-6099-39bc-966320101b03
Version Independent ID: ac21035f-4145-b309-d45c-3c38e965301d
Content: Page layout versions - Azure AD B2C
Content Source: articles/active-directory-b2c/page-layout.md
Service: active-directory
Sub-service: b2c
GitHub Login: @msmimart
Microsoft Alias: mimart

@wouterdevinck, thank you for reaching out. We are looking into this and would get back to you soon on this thread.

@wouterdevinck Thank you for pointing this out. Based on the workaround you have mentioned, I understood that localization for continue button at signup page stops working with Page contract selfasserted 2.0.0.
Apart from that, have you noticed any other built-in strings with the same issue?

The issue occurs for all built-in strings (ux elements, error messages) when switching from selfasserted 1.2.0 to 2.0.0, not just the continue button.

@wouterdevinck I tested this and found that the behavior is different for different languages. When I used ui_locales=nl, localization for all built-in strings was not working and with ui_locales=hi only a few strings were not translated.
Even though there is different impact on different languages, selfasserted 2.0.0 is definitely breaking localization. I will be engaging our Product Team to address the issue.
Could you please send an email with the URL of the issue at azcommunity[at]microsoft[dot]com, so that I can open a free support case and a corresponding ticket with product team to address the issue?

Thank you, I didn't think to test in other languages. Will drop a mail.

Hello there, I can also confirm this issue happening for pt-br language. Thanks.

Open support case:
Support request ID | 120042122000504

@wouterdevinck Thanks for the support case.
I am closing this issue as we use this platform for Document enhancement but we'll keep posting comments to keep the thread up to date until the issue is fixed.

Hello @wouterdevinck, would you please share the support case link? I would like to keep posted about this issue as well. Thanks

I found the same issue, so I had to revert my selfAsserted back to 1.2.0
Thank you

This is fixed now. Kindly check and confirm.

@Feday and @henriquebelotto Have you had a chance to test this out?

Translation of the buttons looks good but the translation on errors not always.
for example this one get auto translated:

but these ones does not get translated:
one time password error 1:

one time password error 2:

Hello @amanmcse I still see strings that are not localized, for example, the email address placeholder and invalid email error message.

authors: 84618315 Feday amanmcse henriquebelotto souravmishra-msft wouterdevinck


text:
Sample code doesn't build

The sample code "Role-base access control for Service Bus" you are linking to on GitHub doesn't build. It would be great if it could be fixed and not just remove link.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0ab42911-035e-3195-6eb7-2096b79f46b2
Version Independent ID: cf3e110d-0a97-1e82-15f6-f03842200d1a
Content: Authenticate an application to access Azure Service Bus entities
Content Source: articles/service-bus-messaging/authenticate-application.md
Service: event-hubs
GitHub Login: @axisc
Microsoft Alias: aschhab

@pihalve
Thanks for the feedback and bringing this to our notice. At this time we are reviewing the feedback and will update the document as appropriate.

@pihalve Could you please share the build error you are experiencing?
Thanks

Yes, and additionally I can say that I'm using Visual Studio 2019 (16.6.2)
1>C:\Sandbox\azure-service-bus\samples\DotNet\Microsoft.ServiceBus.Messaging\RoleBasedAccessControl\Program.cs(29,21,29,29): error CS0234: The type or namespace name 'Identity' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?)
1>C:\Sandbox\azure-service-bus\samples\DotNet\Microsoft.ServiceBus.Messaging\RoleBasedAccessControl\Program.cs(31,27,31,37): error CS0234: The type or namespace name 'ServiceBus' does not exist in the namespace 'Microsoft.Azure' (are you missing an assembly reference?)
1>C:\Sandbox\azure-service-bus\samples\DotNet\Microsoft.ServiceBus.Messaging\RoleBasedAccessControl\Program.cs(32,27,32,37): error CS0234: The type or namespace name 'ServiceBus' does not exist in the namespace 'Microsoft.Azure' (are you missing an assembly reference?)
1>C:\Sandbox\azure-service-bus\samples\DotNet\Microsoft.ServiceBus.Messaging\RoleBasedAccessControl\Program.cs(33,27,33,37): error CS0234: The type or namespace name 'ServiceBus' does not exist in the namespace 'Microsoft.Azure' (are you missing an assembly reference?)
1>C:\Sandbox\azure-service-bus\samples\DotNet\Microsoft.ServiceBus.Messaging\RoleBasedAccessControl\Program.cs(85,37,85,48): error CS0246: The type or namespace name 'QueueClient' could not be found (are you missing a using directive or an assembly reference?)
1>C:\Sandbox\azure-service-bus\samples\DotNet\Microsoft.ServiceBus.Messaging\RoleBasedAccessControl\Program.cs(38,9,38,20): error CS0246: The type or namespace name 'QueueClient' could not be found (are you missing a using directive or an assembly reference?)
1>C:\Sandbox\azure-service-bus\samples\DotNet\Microsoft.ServiceBus.Messaging\RoleBasedAccessControl\Program.cs(39,9,39,20): error CS0246: The type or namespace name 'QueueClient' could not be found (are you missing a using directive or an assembly reference?)
1>Done building project "RoleBasedAccessControl.csproj" -- FAILED.

@pihalve Thanks for sharing the additional details. We have assigned the issue to the content authorto furhter evaluate and update the document as appropriate.
@spelluru Could you please have a look at this feedback? -Thanks.

The sample was fixed a few months ago.
#please-close

authors: KranthiPakala-MSFT pihalve spelluru


text:
A parameter cannot be found that matches parameter name 'ForceDelete'.

Is ForceDelete removed?  I'm sure I've missed something....  Is there another way to do this now?
When copying the command directly from the page and replacing with variables (or strings, either way), I am unable to use the -ForceDelete parameter/switch.
Remove-AzOperationalInsightsWorkspace -ResourceGroupName $rgName -Name $workSpaceName -ForceDelete
Remove-AzOperationalInsightsWorkspace : A parameter cannot be found that matches parameter name 'ForceDelete'.
At line:4 char:87

... orkspace -ResourceGroupName $rgName -Name $workSpaceName -ForceDelete

                                                         ~~~~~~~~~~~~

CategoryInfo          : InvalidArgument: (:) [Remove-AzOperationalInsightsWorkspace], ParameterBindingException
FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.Azure.Commands.OperationalInsights.RemoveAzureOperationalInsightsWorkspaceCommand

Neither does -ForceDelete show up in help
I've installed module version 2.2.0 from the online repository, which has this helpfile for the cmdlet, noticeably absent is the -forcedelete option
PS C:\WINDOWS\system32> help Remove-AzOperationalInsightsWorkspace
NAME
Remove-AzOperationalInsightsWorkspace
SYNOPSIS
Removes a workspace.
SYNTAX
Remove-AzOperationalInsightsWorkspace [-ResourceGroupName] <System.String> [-Name] <System.String>
[-DefaultProfile <Microsoft.Azure.Commands.Common.Authentication.Abstractions.Core.IAzureContextContainer>]
[-Force] [-Confirm] [-WhatIf] []
DESCRIPTION
The Remove-AzOperationalInsightsWorkspace cmdlet deletes an existing workspace. If this workspace was linked to an
existing account via the CustomerId parameter at creation time the original account is not deleted in the
Operational Insights portal.
RELATED LINKS
Online Version:
https://docs.microsoft.com/en-us/powershell/module/az.operationalinsights/remove-azoperationalinsightsworkspace
Azure Operational Insights Cmdlets
Get-AzOperationalInsightsWorkspace
REMARKS
To see the examples, type: "get-help Remove-AzOperationalInsightsWorkspace -examples".
For more information, type: "get-help Remove-AzOperationalInsightsWorkspace -detailed".
For technical information, type: "get-help Remove-AzOperationalInsightsWorkspace -full".
For online help, type: "get-help Remove-AzOperationalInsightsWorkspace -online"

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 86984751-da7f-c77b-c78b-a9c9ffacb4a3
Version Independent ID: 57838082-5ee8-097c-9814-803a5077ba4e
Content: Delete and recover Azure Log Analytics workspace - Azure Monitor
Content Source: articles/azure-monitor/platform/delete-workspace.md
Service: azure-monitor
Sub-service: logs
GitHub Login: @bwren
Microsoft Alias: bwren

@danabrash We are checking this and we will get back to you.

Hi, any update? I have same issue.

The -ForceDelete option was added in version 2.3.0 of the Az.OperationalInsights module (released July 17th), which hasn't made it to the main Az install as yet.
Check which version you have with a 'Get-Module Az.OperationalInsights', you may have to do a 'Install-Module Az.OperationalInsights -RequiredVersion 2.3.0' to install the later version.

Thanks for the reply, @SteveBurkettNZ .
@danabrash  - please let us know if you have any follow-up questions.
We will now close this issue. If there are further questions regarding this matter, please reply and we will gladly continue the discussion.

sorry for re-open, but I wanted to confirm that this was indeed the solution for me.  I have tested and it works perfectly as @SteveBurkettNZ  described.
thank you very much for your help

I have Az.OperationalInsights version 2.3.0 but I am still running into the same issue 'Remove-AzOperationalInsightsWorkspace: A parameter cannot be found that matches parameter name 'ForceDelete'.'

authors: NavtejSaini-MSFT SteveBurkettNZ danabrash femsulu kiennt23 kirasoderstrom


text:
Clarification on how node-image-only works?

Is it possible to clarify in the docs please, will this cause nodes to be reimaged?
And will it also mean that an additional node is added and nodes are drained/cordoned as per a regular upgrade?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 8092825b-b867-d947-9842-f44eba91db00
Version Independent ID: 5b9b865c-0d51-9955-564c-1c898d3150a7
Content: Upgrade Azure Kubernetes Service (AKS) node images - Azure Kubernetes Service
Content Source: articles/aks/node-image-upgrade.md
Service: container-service
GitHub Login: @laurenhughes
Microsoft Alias: lahugh

Thank you @AdamSharif-MSFT for the feedback!
We have added an item to our backlog and will prioritize accordingly.
#please-close

authors: AdamSharif-MSFT zr-msft


text:
Azure App Services supports authentication using Managed Identity

Azure App Services supports authentication with ACR using both managed identities and service principals based on these docs:
https://github.com/Azure/app-service-linux-docs/blob/master/HowTo/use_system-assigned_managed_identities.md
https://github.com/Azure/app-service-linux-docs/blob/master/service_principal_auth_acr.md
Please update this doc to reflect this.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 9d1bf6a2-95e7-4b50-e03e-9bf212dc5214
Version Independent ID: 79ee1b51-6a22-0a57-2a28-7eb5a65c9778
Content: Authenticate with managed identity - Azure Container Registry
Content Source: articles/container-registry/container-registry-authentication-managed-identity.md
Service: container-registry
GitHub Login: @dlepow
Microsoft Alias: danlep

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

#assign: @tejaswikolli-web

@Ahmad-Al-Ali, can you confirm if this is the article you are looking for?
https://docs.microsoft.com/en-us/azure/container-registry/container-registry-auth-service-principal

https://docs.microsoft.com/en-us/azure/container-registry/container-registry-auth-service-principal
https://docs.microsoft.com/en-us/azure/container-registry/container-registry-authentication-managed-identity
App services support both the service principle and managed identity. I hope this answers your question.
#please-close


text:
This page need to be updated.

The options available in subnet are not there like NAT gateway setting. Additionally there is no USERS setting in the subnet level.
[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b8332806-35c4-26e5-56e6-0286d728ad45
Version Independent ID: ce76cee4-5629-7439-309c-9b9705891b57
Content: Add, change, or delete an Azure virtual network subnet
Content Source: articles/virtual-network/virtual-network-manage-subnet.md
Service: virtual-network
GitHub Login: @KumudD
Microsoft Alias: kumud

Hello @kdupindersingh,
Thank you for your feedback! We have assigned this issue to the author to review further and take the next course of action.

👍
On Fri, 6 Aug 2021 at 3:10 am, ChaitanyaNaykodi-MSFT <
@.***> wrote:

Hello @kdupindersingh https://github.com/kdupindersingh,
Thank you for your feedback! We have assigned this issue to the author to
review further and take the next course of action.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/79357#issuecomment-893715600,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APXWECUAMOMYTUZEZOSSF23T3LOYXANCNFSM5BUL5FFQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

#reassign: @mbender-ms

#please-close


text:
Branch is main or master?

Why are some of the branch names in troubleshooting main and some master?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 8e94f3fb-7da7-3ddf-bf38-32e4fea00699
Version Independent ID: 59222ad8-9930-b889-f0a9-c9bc3c642e38
Content: Deploy from local Git repo - Azure App Service
Content Source: articles/app-service/deploy-local-git.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

@diberry Thanks for the question. We're investigating this and will get back to you shortly.

Hey,
I think the naming, especially of Azure DevOps repositories, changed in the past from master to main:
https://devblogs.microsoft.com/devops/azure-repos-default-branch-name/

@diberry As @kaiaschulz mentioned above, Azure DevOps has renamed the default branch of new repositories from master to main in an effort to move towards a more inclusive language. More details in the referenced blog above.
That said, I have submitted a PR to replace the remaining occurrences of master to main in this How-To guide that's in review. Thanks again for bringing this to our attention.

@diberry @BhargaviAnnadevara-MSFT I'm currently changing the names strategically. Please don't make any systematic changes because App Service still uses master as the default branch and telling customers to just push with a different command will just result in deployment failure.

@diberry any "main" you see in our docs is most likely from someone other than us doing bulk changes. it doesn't actually help our docs.

@cephalin Here is the commit/PR I referred to: https://github.com/MicrosoftDocs/azure-docs-pr/pull/142092 from about 6 months ago. There was also a User story linked within.
#reassign:cephalin

Added a section in the doc to explain between master and main and fixed some of the discrepancies. #please-close

authors: BhargaviAnnadevara-MSFT cephalin diberry kaiaschulz


text:
No option "Add training data to train keyword model" for custom keyword

[Enter feedback here]
in this screenshot, there is an option "Add training data to train keyword model"

https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/media/custom-keyword/custom-kws-portal-choose-prons.png
but in speech studio, there is no place to find this option.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 02f19f0c-f14b-bac9-3706-93c888eb3bb2
Version Independent ID: ed76fd34-0256-eb27-a55f-5d2735859f98
Content: Create Keyword quickstart - Speech service - Azure Cognitive Services
Content Source: articles/cognitive-services/Speech-Service/custom-keyword-basics.md
Service: cognitive-services
Sub-service: speech-service
GitHub Login: @eric-urban
Microsoft Alias: eur

@kinosong Thanks for the question. We are investigating the issue and will update you shortly.

@eric-urban Thanks, Could you please check the below issue to update the document.

@kinosong @ram-msft - Thanks for letting me know. Speech studio UI has changed over time, and I will refresh the documentation to catch up.

@kinosong @ram-msft - Doc has been updated. Thanks again.

#please-close

authors: eric-urban kinosong ram-msft


text:
Clarity around use Log Analytics and SQL Analytics

My understanding (and I could be wrong) is that the only log destination supported for SQL Analytics is Azure Log Analytics workspace. Could we get some more clarity in the doc to support that, if it is indeed an accurate statement? Thanks

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 77f273ec-aed5-1f65-0b6d-87240765d3e0
Version Independent ID: d195959f-5742-7d94-f4f5-e70c0f0581e7
Content: Azure SQL Analytics (preview) solution in Azure Monitor - Azure Monitor
Content Source: articles/azure-monitor/insights/azure-sql.md
Service: azure-monitor
Sub-service: insights
GitHub Login: @danimir
Microsoft Alias: danil

@jdanton Thanks for your comment! We will review and provide an update as appropriate.

Destinations can be: Log analytics, Blob Storage, and Events hub.

@danimir Thanks for the comment.
@jdanton At this point it appears that there's no edits or updates needed for the referred Azure documentation soc losing this issue for now. If there are further questions regarding this matter or feedback on the referred Azure documentation, please do let us know and we will gladly continue the discussion.

authors: KrishnaG-MSFT danimir jdanton


text:
ACU values not yet posted for latest Intel Ice Lake processors Ev5 / Dv5

[Enter feedback here]
Hi azure-docs team, the latest Intel Ice Lake processors have GA-ed for a while. However, the ACU corresponding to the new SKU's have not been published yet.
Could you please share the plans when the ACU values for the new Ice Lake processors will be published?
Thanks, Darko
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 568a0854-5b9e-0d79-642f-2775271d0521
Version Independent ID: 876df17a-3a80-8e2d-bb70-c6810df7fd18
Content: Overview of the Azure Compute Unit - Azure Virtual Machines
Content Source: articles/virtual-machines/acu.md
Service: virtual-machines
Sub-service: sizes
GitHub Login: @mimckitt
Microsoft Alias: mimckitt

@mocelj Thank you for your feedback!  We've assigned this to the document author for further review.

We are currently reevaluating how we calculate Azure Compute Units weights for our Virtual machine performance benchmarks to account for updates in processor architecture from our CPU providers.
Docs will be updated accordingly as information becomes available.
#please-close

Hi All,
Any update about posting the documentation update?
Regards,
LM

authors: LeoYMCMB kobulloc-MSFT mimckitt mocelj


text:
Parameter misspelt

Parameter 'DiskEncryptionSecretUrl'  misspelt for Example 7 on this link .

@devsheoran - Thanks again for bringing this to our attention. We have updated the Doc and it will be live once its merged.  We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

authors: MonikaReddy-MSFT devsheoran


text:
clarify data lake name should be in the spark config.

[Enter feedback here]
It would be good to clarify in the spark configs that you have to include the data lake name.  For instance
fs.azure.account.oauth2.client.id.acmeadls.dfs.core.windows.net <application-id>

would be clearer if it were
fs.azure.account.oauth2.client.id.<datalakename>.dfs.core.windows.net <application-id>

It would also be better if this clarified there will need to be entries for each data lake name and that these settings will be used for anyone using that cluster.  So even if areas are mounted using pass-through on the cluster queries will be run as the SPN rather than the end user.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ae18d575-4a87-7079-c16d-23259c5b8d5e
Version Independent ID: 4d4e97dd-444d-a5df-e77a-0d0cc594f08f
Content: Tutorial: Run a job with an Azure service principal - Azure Databricks
Content Source: databricks/tutorials/run-jobs-with-service-principals.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

Thanks for providing feedback that helps improve our documentation. This issue has been resolved and we are closing the issue.
#please-close

#please-close

authors: JasonWHowell MasterAslan kateglee-db


text:
Document describe of constraints

It would be good to document the command to describe a separate constraint:
kubectl describe {constraint kind} {constraint name}
(and how to get the constraint kind.)

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b1d98d35-46d2-eb6f-6a0b-21df4d6438a8
Version Independent ID: 1a7a0c68-fa1c-d457-2be9-a919d4a5e64f
Content: Learn Azure Policy for Kubernetes - Azure Policy
Content Source: articles/governance/policy/concepts/policy-for-kubernetes.md
Service: azure-policy
GitHub Login: @timwarner-msft
Microsoft Alias: timwarner

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

Okay, @perentorio, I'll add a couple kubectl examples in the document tomorrow morning. Thanks for the suggestion! Kindest regards, Tim

#please-close

authors: RyanHill-MSFT perentorio timwarner-msft


text:
Make available Mongo version to 4.2

[Enter feedback here]
Added support for Mongo version to 4.2 and update the documentation. A couple of places shows only 3.2 and 3.6
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: dc075caf-933b-cda0-703b-6b700f1436f8
Version Independent ID: 102753f5-d177-627e-c14c-e88df91c8000
Content: Resource Manager templates for Azure Cosmos DB API for MongoDB
Content Source: articles/cosmos-db/mongodb/resource-manager-template-samples.md
Service: cosmos-db
Sub-service: cosmosdb-mongo
GitHub Login: @markjbrown
Microsoft Alias: mjbrown

@jjpinto Thank you for your feedback. We are reviewing this and will get back shortly.

@markjbrown is the documentation only for Mongo version 3.2 or 3.6

Quick update.
The ARM and Bicep samples within our docs are actually located in the Azure Quickstart GitHub Repository here.
The samples on GitHub have both regular Azure Cloud and Gov Cloud included parameter files. During PR these are built and deployed to both clouds and must pass to be merged. The PR's to update these to 4.2 are failing because we do not yet have support for Mongo 4.2 in our Gov Cloud. End result is we cannot update our samples until that support gets deployed.
I have an ask into my team for an ETA on when this will happen. Once the support is deployed we will merge these changes which will update the docs. I don't have an ETA on this unfortunately so cannot provide that here.
I am however going to close this docs issue for now as we have PR's in place to do this update.
Thanks for your feedback. We very much appreciate it.
#please-close

authors: Oury-MSFT jjpinto markjbrown


text:
Saving other types of batch inference output

In the ML Studio batch inference endpoints, how can I save the output from semantic segmentation models? The documentation explains how to get generic data from blob storage but seems to be missing how to save my output data (in this case semantic segmentation masks) to a corresponding blob storage location.

Document details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f24ec969-b354-a6ee-fde3-0b7e478a7827
Version Independent ID: 316e0373-e365-3e42-0529-850c06030b2b
Content: Use batch endpoints for batch scoring - Azure Machine Learning
Content Source: articles/machine-learning/how-to-use-batch-endpoint.md
Service: machine-learning
Sub-service: mlops
GitHub Login: @Blackmist
Microsoft Alias: larryfr

Thanks for the feedback! We are currently investigating and will update you shortly.

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

@davystrong , currently we expose only one output for whole batch, although we're internally creating output for each process and merge later. For the time being, using Pipeline should work.

@dem108 sorry for the delay! I must have missed the notification in everything else. I think using pipelines for batch inference would work in the meantime, thanks! I ended up using the SDK to "manually" upload a dataset, this would probably be cleaner.

Thanks for your confirmation! Great to hear the alternative works for you now. If you see any other issues, please don't hesitate to create them separately. Have a nice day!
#please-close

authors: YutongTie-MSFT davystrong dem108


text:
Link for Azure AD Graph Explorer is not working

The linked Azure AD Graph Explorer: "Also, you can test this in the Azure AD Graph Explorer, and the Microsoft Graph Explorer by using your Azure AD account." with the URL https://graphexplorer.cloudapp.net is not working. I suppose, the link changed to: https://graphexplorer.azurewebsites.net

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 02ff3d62-dc0e-ad0c-f5ae-418337cf31e4
Version Independent ID: d50952b5-6b98-c40d-d3a3-f9cbec58dd28
Content: Configurable token lifetimes in Azure Active Directory
Content Source: articles/active-directory/active-directory-configurable-token-lifetimes.md
Service: active-directory
Product: unspecified
GitHub Login: @hpsin
Microsoft Alias: hirsin

@denishol Thanks for your feedback! We will investigate and update as appropriate.

@denishol The PR for the fix has been created and it will be merged soon. Thanks again for pointing this out, I am closing the issue based on this update, please let us know if there is something else that we can help you with.

authors: SaurabhSharma-MSFT denishol


text:
ARM sample for configuring diagnostic settings for the new Front Door

[Enter feedback here]
Hi,
Could you please add ARM samples for configuring diagnostic settings for the new Front Door to this page? or provide it here? We need to log to an Azure Log Analytics workspace, and the ARM for the classic frontdoor does not work.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ea673aa4-1e06-c7a4-c86a-ab949e46394e
Version Independent ID: 7fbe7485-538d-7c0e-d219-41ead79fb38f
Content: Azure Resource Manager template samples - Azure Front Door
Content Source: articles/frontdoor/front-door-quickstart-template-samples.md
Service: frontdoor
GitHub Login: @duongau
Microsoft Alias: duau

Thank you for your feedback! We have assigned this issue to the author to review further and take the next course of action.

authors: ChaitanyaNaykodi-MSFT zaalion


text:
Wrong registry information to "CloudKerberosTicketRetrievalEnabled" key

#Configure the clients to retrieve Kerberos tickets
Create the following registry value on the client(s): reg add HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters /v CloudKerberosTicketRetrievalEnabled /t REG_DWORD /d 1

The command line for adding registry value should be "reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters /v CloudKerberosTicketRetrievalEnabled /t REG_DWORD /d 1"

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: eed4f875-3115-073b-5ffd-3b31eaf0205f
Version Independent ID: a7476b7f-fce3-474f-6a1f-558321768c15
Content: Use Azure Active Directory to authorize access to Azure files over SMB for hybrid identities using Kerberos authentication (preview)
Content Source: articles/storage/files/storage-files-identity-auth-azure-active-directory-enable.md
Service: storage
Sub-service: files
GitHub Login: @khdownie
Microsoft Alias: kendownie

@sparkf1
Thanks for your feedback! We will investigate and update as appropriate.

@khdownie
Can you please check and add your comments on this doc update request as applicable.

@sparkf1 You're saying you should write to the GP location instead of the system location. We honor both methods, and the system location is documented so the user doesn't have the value blown away by policy changes. It should be noted that changes to either location are not instant and require a policy refresh or a reboot to take effect. Can you tell me why writing to the system location didn't work for you? Thanks!

#please-close

authors: SaibabaBalapur-MSFT SouravDutta-MSFT khdownie sparkf1


text:
remove .Net 5 requirement

Dotnet 5 is not needed, and should not be included in the pipeline.
This PR makes the learn docs mirror what's stated at the GitHub repo as well as the Marketplace documentation

@elazark
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@bjompen I am reaching out to the relevant stakeholder sot see if they are ok with removing this.

@bjompen I spoke with the appropriate stakeholders and they informed me that .net 5 is needed and that it should not be removed. Thank you for taking the time to make this suggestion but at this time I can't remove it form the yaml file.

#please-close

source: gharchive/pull-request

authors: Court72 ElazarK bjompen


text:
Update benefits-of-migrating-to-hdinsight-40.md

Added storage warning for partition discovery

Closing this PR because the change was already merged to main.


text:
test commit 1, do not merge

Test PR, do not merge.

@rmca14 : Thanks for your contribution! The author, @MarkusVi, has been notified to review your proposed change.

@MarkusVi
Hi, Markus -- please ignore this PR and auotmated request for review. This PR is testing the system. Thanks.


text:
Update deviceOwnership from Corporate to Company

The value "corporate" do not create any results for Dynamic groups in Azure AD, this value is applicable for Intune.
The correct value for the group is "Company"

Hi @pedrog-msft
That's already been changed to companyName, and to the best of my knowledge that is the correct value. Can you try that?

Hello @curtand
Thank you for your message.
I did a double check and I still see the "corporate" mention instead of "company".
Device attribute	Values							Example
deviceOwnership		Personal, Corporate, Unknown	(device.deviceOwnership -eq "Corporate")
https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/active-directory/users-groups-roles/groups-dynamic-membership.md#rules-for-devices
Thank you.

OK @pedrog-msft thanks. I was looking at a different change and didn't spot the disparity. I"ll confer with PM and get this fixed.

#sign-off

authors: curtand pedrog-msft


text:
Update virtual-wan-faq-include.md

Capitalize Azure (proper noun)

@ciphertxt : Thanks for your contribution! The author, @cherylmc, has been notified to review your proposed change.

Verified editorial correction.

authors: PRMerger14 ciphertxt rjagiewich


text:
Update active-directory-assign-admin-roles-azure-portal.md

Added conditional access administrator role.

@VinceSmith,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@VinceSmith : Thanks for your contribution to the Azure documentation! The author, @curtand, has been notified to review your proposed change.

#sign-off

authors: PRmerger VinceSmith curtand msftclas


text:
Update point-to-site-about.md

Clarified ambiguous verbiage around firewall port 443 for IKEv2 and OpenVPN P2S connection. Updated to explain that port 443 outbound access is needed.

@caseywatson : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thanks, @caseywatson! #sign-off

authors: PRMerger16 caseywatson cherylmc


text:
Update load-balancer-custom-probe-overview.md

Updating requirements for HTTP probe. SHA-1 is no longer supported.

@streetratz : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#please-close
Fixed via private PR.

authors: PRMerger20 anavinahar streetratz


text:
Server Core OS -update

Server Core OS doesn't support any type of device registration

@NagaCSC : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

authors: MicrosoftGuyJFlo NagaCSC PRMerger19


text:
feat: Licensing Service Plan Reference Formats

Supply the Licensing Service Plan Reference table as different formats - CSV / JSON.
This is in lieu of waiting for MS to update Graph API to include the Portal 'friendly' names as requested here: https://feedback.azure.com/forums/169401-azure-active-directory/suggestions/37398988-add-a-friendly-name-attribute-when-getting-msol-li
https://github.com/MicrosoftDocs/azure-docs/issues/49024

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: jdelforno sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Hi @daveba - As business approver for Azure Active Directory, could you review this pull request?
cc @SyntaxC4
Thanks.

authors: jdelforno ktoliver msftclas


text:
Fix topology url

Fix topology url to point to the raw json file

@naiteeks : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

authors: Juliako PRMerger16 naiteeks


text:
Updated to point to stable version of service bus samples

Service Bus Track 2 v 7.0.0 is already releases.
We should point to stable version now instead of pointing to samples/preview

#sign-off

#sign-off

@spelluru: I'm sorry - only the author of this article, @axisc, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

authors: PRMerger14 hemanttanwar spelluru


text:
Incorrect file size

The actual information displayed by Microsoft within the branding section is misleading/incorrect.  It says "File size: <300KB" which is 307,200 Bytes. When you have an image file that Windows shows is 299KB (306,176 Bytes) the Azure portal rejects the image as too large with an error displayed that says "Selected file  must be between 1 and 300000 bytes" which is less than 293KB.  I know this is not the correct way to get the actual portal functionality updated so let's update the documentation to reflect what the portal actually accepts. The problem is caused by the use of KB = 1024 bytes or 1000 bytes and is inconsistent.

@mprentice22153 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@ShannonLeavitt : Thanks for your contribution! The author(s) have been notified to review your proposed change.


text:
Update marketplace-solution-templates.md

Freshness review. Content is still accurate.

@AarathiN : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi @AarathiN Are you a Microsoft PM? If you are, you can work in the private repository if you complete the steps in the Get started section of the Microsoft-internal contributor guide. That would be a better place to complete freshness updates. I can send you a link if needed.

#sign-off
@AarathiN
Please use the private repo in the future please azure-docs-pr.
Do we need to check off the freshness deliverable/task for this page?
CC: @jasongroce

authors: AarathiN JasonWHowell PRMerger16 ktoliver


text:
Global Catalog access is needed to enable Azure Active Directory Seam…

…less Single Sign-On
Without access to the GC the scripts to enable Azure Active Directory Seamless Single Sign-On seen at https://docs.microsoft.com/en-us/azure/active-directory/hybrid/tshoot-connect-sso#manual-reset-of-the-feature do not work because the cmdlets report "[time] [  9] [INFORMATIONAL] GetDesktopSsoComputerAccount: Searching in global catalog(forest) and ad.dcsadvisory.com for computer account AZUREADSSOACC" and then fail to connect. Once GC ports are open this works immediately. Therefore proposing that this is added to this table

@brianreidc7 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

This is going to be included in an overall update to the doc. This item has been captured. At this point we can close this as it will probably be another month or so. We need to address the images as well. Thanks!
#please-close


text:
Update Create Documo test user section

Rewrite to accurately show the add user process without just-in-time provisioning.

@djllap : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

#sign-off

authors: PRMerger7 djllap jeevansd ktoliver


text:
Update virtual-machine-scale-sets-health-extension.md

Adding additional properties to the schema.

@am4234m : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@am4234m: I'm sorry - only the author of this article, @ju-shim, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

Hi @am4234m - This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. We can keep this PR open for review and merge, but would you make future content updates in the private repo? Thank you!
(In this repo, authors need to sign off on pull requests.)

#sign-off


text:
Update azure-monitor-agent-supported-operating-systems.md

updating azure linux to azure linux 3.0
updating disk size message to be non-release specific

@guywi-ms
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off

authors: Jak-MS flora-taagen guywi-ms

repo: MicrosoftDocs/azure-monitor-docs


text:
PowerShell instructions are not clear

[Enter feedback here]
Instructions are not clear. In the cmdlets below, there is no reference from where the variable $vm is coming from. I would imagine that the first one is from "Get-ClusterResource -Name "Virtual Machine xyz"? The next cmdlet cannot be piped, so should I use "Add-VMAssignableDevice -ResourcePoolName GPU_Pool -VMName xyz?
$vm | Set-ClusterParameter -Name "OfflineAction" -Value 3
$vm | Add-VMAssignableDevice -ResourcePoolName "GpuChildPool"
I was able to assign the GPU from a Pool to a VM and install the GPU drivers, however VM wont move to remaining node if I Pause node it is running on.
Error:
Move of cluster role 'xyz' for drain could not be completed.  The operation failed with error code 0x32.
Please provide instructions so it can be retried.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c08dae85-343a-8053-316f-fa321a0c46dc
Version Independent ID: e91c7aa1-e79b-752b-f9ae-7f29d9629ae2
Content: Use GPUs with clustered VMs - Azure Stack HCI
Content Source: azure-stack/hci/manage/use-gpu-with-clustered-vm.md
Service: azure-stack
Sub-service: azure-stack-hci
GitHub Login: @rick-man
Microsoft Alias: rickman

I decided to manually stop the VM and then I performed a Quick Migration in order to move VM pointer to the other node, since Drain/Pause node failed. VM started just fine on the other node and GPU was present.

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

Sounds like the issue was resolved.

repo: MicrosoftDocs/azure-stack-docs


text:
Personal/jebearer/lts

updates to amlfs client code

@pauljewellmsft

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off

authors: Jak-MS jeffbearer pauljewellmsft


text:
Update move-an-analysis-services-database.md

Adjusted the step numbering

@microsoft-github-policy-service agree

@Minewiskan
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

repo: MicrosoftDocs/bi-shared-docs


text:
Missing code for connecting with Direct Line Speech endpoint in javascript

I searched a lot but couldn't find any documentation on how to connect with the direct line voice chat api. What is the endpoint for connecting to direct line speech api? Existing docs mention only direct line chat api.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: aa4cb4da-ca0e-fc7f-686c-f3510bf9af0b
Version Independent ID: e20d2896-dcec-8e46-2f50-2227def34250
Content: Connect a bot to Direct Line Speech (Preview) - Bot Service
Content Source: articles/bot-service-channel-connect-directlinespeech.md
Service: bot-service
Sub-service: bot-service
GitHub Login: @trrwilson
Microsoft Alias: travisw

Hi Mitul,
you might want look at this article : Connect a bot to Direct Line Speech (Preview).

Mitul, thank you for contacting us.
Are you having problems with this article: Connect a bot to Direct Line Speech (Preview)? You mention also "direct line voice chat api". Could you please clarify the kind of issue you are experiencing?

Please, refer to the new doc version at  Connect a bot to Direct Line Speech (Preview). The technology is still in preview mode and we are continuously updating the related docs.

authors: mitulsuthar mmiele

repo: MicrosoftDocs/bot-docs


text:
GET /v3/conversations returns 405 http code

GET /v3/conversations returns 405 HTTP code but should return a list of conversations the bot has participated in (according to this https://docs.microsoft.com/en-us/azure/bot-service/rest-api/bot-framework-rest-connector-api-reference?view=azure-bot-service-4.0#get-conversations)
Steps to reproduce the behavior:

Get access token
Perform GET /v3/conversations
See the response

Request:
GET /amer/v3/conversations HTTP/1.1
Authorization: Bearer {access_token}
Host: smba.trafficmanager.net
Connection: close
User-Agent: Paw/3.1.8 (Macintosh; OS X/10.15.0) GCDHTTPRequest

Response:
HTTP/1.1 405 Method Not Allowed
Allow: POST
Content-Length: 72
Content-Type: application/json; charset=utf-8
Server: Microsoft-HTTPAPI/2.0
Date: Fri, 20 Sep 2019 12:31:51 GMT
Connection: close

{"message":"The requested resource does not support http method 'GET'."}

Additional context
This issue looks like #1264
I tried two endpoints: https://smba.trafficmanager.net/apis and https://smba.trafficmanager.net/amer.
Also, tried different networks and routings.
Clients: Paw and Postman.
Feel free to ask any additional details.

@apetrovs What channel are you trying to use?

Closing due to inactivity.

@tdurnford Hey! Sorry for the late reply. What do you mean by "channel"?
I use https://smba.trafficmanager.net/amer as the service URL because I receive it in incoming events. And https://smba.trafficmanager.net/apis was mentioned in #1264, so I decided to try it also.

By channel I mean the BotFramework supported channels - Teams, Skype, Facebook Messenger, Line, Direct Line, etc. Basically how are you interacting with your bot?

@tdurnford thanks for the explanation. My bot is for Teams and I use the Java framework and REST API.

It appears that most channels do not support the get conversation endpoint which is why the request is responding with a 405 error. From what I can tell, Direct Line is the only channel that supports the request. This is not well documented unfortunately. Take a look at https://github.com/microsoft/BotFramework-Services/issues/88 for more details.

@JonathanFingold I am using GET Conversations in Teams, and it returns "Method not allowed". You mentioned "Please comment on that thread, and we'll try to get you unblocked". What do I need to do to get this unblocked for my bots?

@tdurnford thanks for the information! But it would be great if that appears in documentation.

@JonathanFingold I am using GET Conversations in Teams, and it returns "Method not allowed". You mentioned "Please comment on that thread, and we'll try to get you unblocked". What do I need to do to get this unblocked for my bots?

@tdurnford Can you also help @dgancho ? If it's more convenient, feel free to reopen the other issue I closed as a duplicate of this one.

@JonathanFingold It is the same issue. The get conversations get request does not support the Teams Channel. I don't believe there are any plans to change this behavior.

Can you please take a look at this related issue - https://github.com/MicrosoftDocs/bot-docs/issues/1934 ?

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close

authors: JonathanFingold apetrovs dgancho erhopf penguinsource tdurnford


text:
naming & tagging convention template - Naming convention inconsistencies

First of all thanks a lot for providing the Naming & Tagging standard template!
While studying the template, I noticed the following naming inconsistencies:

In the "intro and components" sheet, virtual machines are prefixed with vm-, while in the "Naming convention" sheet the format and example is missing the dash (vm<policy name or appname><###> / vmsharepoint001)

Also the question arises whether the VM number (<###>) wasn't supposed to be separated by a dash as with most other assets.

In the "Naming convention" sheet under Virtual Machines the format and the example for the entries of the  Load Balancer  and  NIC do not match (dash)

lb-<app name or role><Environment><###> / lb-sharepoint-dev-001
nic-<##>-<vmname>-<subscription><###> / nic-02-vmhadoop1-prod-001

General question:
In the "intro and components" sheet most resource name prefixes include a dash (-) as the last character, while some are lacking one (e.g. stor, ssimp, dls, dla and pbiemb). Do they use a different schema intentionally and if yes, is there a technical limitation or similar to it, which could be noted as a comment in the sheet? The same question goes for the <Environment> separation of those assets in the "Naming convention" sheet.
Thanks!

I'm very sorry, I opened this issue in the wrong repository. Will close it here and re-open one in https://github.com/microsoft/CloudAdoptionFramework/ instead.

repo: MicrosoftDocs/cloud-adoption-framework


text:
Repo sync for protected CLA branch

The pull request is created from master637558336008187020 to master to fix git push error for protected CLA branch

@v-alje : Thanks for your contribution! The author(s) have been notified to review your proposed change.

repo: MicrosoftDocs/cpp-docs


text:
Repo sync for protected CLA branch

The pull request is created from main637829607038848117 to main to fix git push error for protected CLA branch

Microsoft authors of articles need to make updates through the private repository, so the updates can be staged and validated by current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the PR reviewers know the updates are ready to be merged.
It's easy to access the private repo version of your articles in GitHub. Just add -pr to the URL, as follows:
 Public repo URL: https://github.com/MicrosoftDocs/{docs-repo}
 Private repo URL: https://github.com/MicrosoftDocs/{docs-repo-pr}
We have closed this pull request. Please resubmit the updates through the private repo. For more information, see the contributor guide.

repo: MicrosoftDocs/dataexplorer-docs


text:
manage subject tree mismatch

Is there a possibility this documentation references a control that has not been made available yet?
We are on the latest release wave with all updates installed, but I can't seem to find the controls mentioned in this article anywhere.
regards

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c94d7763-28b5-f1cd-f5f9-f42cefd7b5d9
Version Independent ID: 3ebc0392-c881-fc5b-10fd-7d7731114226
Content: Create and manage subject tree (Dynamics 365 Customer Service)
Content Source: ce/customer-service/create-manage-subject-tree.md
Service: dynamics-365-customerservice
GitHub Login: @neeranelli
Microsoft Alias: nenellim

Thank you for reaching out, @strwase.
Please let me know in which region your Customer Service instance is deployed. I understand that the feature is being rolled out in a phased manner in the supported geo locations, such as Canada. If your instance is deployed in the US, you might not yet be able to view the feature. Please let me know so that I can get you accurate information.
Best regards,
Neeraja

Hi,
I am using Europe region on 2 different tenants and one of them has the feature enabled.
This is the first env:

On the other one i am not able to see the new interface but the old one:

Do you know why on some tenants The feature is enabled and on some not?
Thank you,
Eduard

Hi @strwase,
I have installed the last version too yes, wave 1 2022, but I don't think this is the issue cause I have another tenant where the version is wave 2 2021 and the control is updated like in the first picture.

@strwase,
I hope that your issue is resolved and you can view the new features in the subject tree. If not, your issue might need product support. To contact Microsoft Support, consider one of the options described here: https://docs.microsoft.com/dynamics365/get-started/support/
Best regards,
Neeraja

authors: neeranelli razxssd strwase


text:
Example seems to suggest that MaxLength is encapsulated in the Comment property

This example:
Label 'ALLOWED POSTING DATE', Comment='{MaxLength=30}'
seems to suggest that MaxLength it not a separate label property, but is encapsulated in the Comment property.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a15813f6-f9d6-5008-5d18-c69fd4f0f761
Version Independent ID: 0ac4ae64-4482-818b-b0fd-0b59f7d7a962
Content: Label Data Type - Business Central
Content Source: dev-itpro/developer/methods-auto/label/label-data-type.md
Service: dynamics365-business-central
GitHub Login: @SusanneWindfeldPedersen
Microsoft Alias: solsen

Thanks for catching this, the example is misleading and will be fixed with the next doc refresh.

authors: SusanneWindfeldPedersen jhoek


text:
ListPage

It does not seem to apply to ListPages, this would be a nice addition.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c40fcac6-97a5-2b0f-b5a3-bf5815a1c0a1
Version Independent ID: c02b891a-fc05-9f98-004a-894e968f4efb
Content: QuickEntry Property - Dynamics NAV
Content Source: dynamics-nav/QuickEntry-Property.md
Service: unspecified
Product: dynamics-nav-2018
GitHub Login: @jswymer

Thanks for the feedback.
The QuickEntry property should work on lists in the Windows client. However, it is ignored on lists in the Web client. What client were you using?
I have updated the article to include the Web client limitations. It will be available soon.
Thanks again

authors: jswymer pungggi


text:
Cannot find "Print Receipt on Giro" on the Document tab "Sales & Receivables Setup"

Depreciated?
https://docs.microsoft.com/gl-es/dynamics-nav/deprecated-features-no?view=dynamicsnav-ps-2018

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c64c217e-3dfa-cc25-672d-080d46e9f2f8
Version Independent ID: ff78d303-58b3-eac8-e4ab-fd435f2d9fbc
Content: How to Set Up KID Numbers on Sales Documents - Business Central
Content Source: business-central/LocalFunctionality/Norway/how-to-set-up-kid-numbers-on-sales-documents.md
Service: dynamics365-business-central
GitHub Login: @SorenGP
Microsoft Alias: sgroespe

Thank you for the feedback. The description of Print Receipt on Giro field has been removed. The update will be available within one week.

authors: SorenGP cghasvi


text:
Update tutorial-enable-azure-mfa.md

The path to the policies in section Clean up resources should contain 'Policies' instead of 'Protection'
Existing:
Browse to Protection > Conditional Access, and then select the policy that you created, such as MFA Pilot.
Should be:
Browse to Policies> Conditional Access, and then select the policy that you created, such as MFA Pilot.

@Justinha
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off

repo: MicrosoftDocs/entra-docs

license: MIT


text:
TOM documentation web pages are missing.

All of a sudden the TOM documentation web pages are missing. Browse for ITextRange2 and you get a 404 message. These are important documentation web pages for the RichEdit control used extensively internally and externally in Windows and Office. Please get them back on line. For example, go to https://docs.microsoft.com/en-us/windows/win32/controls/text-object-model and click on ITextDocument or other interfaces. Up comes the 404 message.

Hi, thanks for getting in touch. I believe this was a temporary problem and the links are all functional again. If not, please let us know!

authors: GrantMeStrength MurraySargent

repo: MicrosoftDocs/feedback


text:
Can not access DMA download page.

Describe the bug
We can not access DMA download page with "Gateway timeout".
https://www.microsoft.com/en-us/download/details.aspx?id=53595
To Reproduce
See error
Gateway Timeout
The proxy server did not receive a timely response from the upstream server.
Reference #1.bb6e2317.1590461588.1b768896

Thank you.
I can access this site now.

@hiobay Download at https://download.microsoft.com/download/C/6/3/C63D8695-CEF2-43C3-AF0A-4989507E429B/DataMigrationAssistant.msi
#please-close

authors: hiobay rootsmusic


text:
Identity API not supported at Windows Outlook Client (Office.js)

Describe the bug
I am using the "getAccessToken" function inside my Outlook Add-in (Office.js).
At the OWA it works but on the Windows Native Client an exception was thrown:
{code: 13012, message: "Die API wird in dieser Plattform nicht unterstÃ¼tzt.", name: "Nicht unterstÃ¼tzte API."}
At the requirements for the identity API (https://docs.microsoft.com/de-de/office/dev/add-ins/reference/requirement-sets/identity-api-requirement-sets) the declared support for the Windows Native client with an Office 365 subscription is 2008 (Build 13127,20000) or newer, my current version is 2101 (Build 13628.20274)
To Reproduce
Steps to reproduce the behavior:

Create an Outlook Add-in with Office.js
Call the method 'getAccessToken'
Install and open the add-in at the Windows Native Client
Use the Add-in until the 'getAccessToken' function has been executed and see the error at the console inside the Edge DevTools Preview that are attached to the Add-in

Expected behavior
The same behavior as the OWA, don't throw an exception and return a bootstrap access token that can be exchanged with the "on behalf of" flow at the Azure OAuth2 token endpoint.
Desktop

OS: Windows 10 version 1909 (Build 18363.1316)
Browser OWA -> Chrome | Native -> Windows Outlook Client 2101 (Build 13628.20274) (Edge version 44.18362.449.0)

@Bjoern01 Please submit feedback by clicking on the button at the doc's bottom.

Hello,
We are experiencing the same exact issue. Is there an ETA for the fix?

authors: Bjoern01 georgechr rootsmusic


text:
K2T_in_Articles

K2T Doc is added into articles

Docs Build status updates of commit 14131c9:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Articles/Actions/K2T_Documentation.md
:warning:Warning

Details

Articles/images/K2T_Acion_Logo.png
:white_check_mark:Succeeded

Articles/images/K2T_Add_button.png
:white_check_mark:Succeeded

Articles/images/K2T_Page_App_overview_Icon.png
:white_check_mark:Succeeded

Articles/Actions/K2T_Documentation.md

Line 1, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 29, Column 1: [Warning-file-not-found] Invalid file link: './Articles/images/K2T_Page_App_overview_Icon.png'.
Line 42, Column 258: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/concepts/deploy-and-publish/apps-upload' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 44, Column 5: [Warning-file-not-found] Invalid file link: './Articles/images/K2T_Add_button.png'.
Line 65, Column 1: [Warning-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
Line 69, Column 1: [Warning-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
Line 73, Column 1: [Warning-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
Line 80, Column 1: [Warning-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
Line 92, Column 1: [Warning-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
Line 99, Column 1: [Warning-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
Line 106, Column 1: [Warning-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
Line 1, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.
Line 42, Column 258: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/en-us/microsoftteams/platform/concepts/deploy-and-publish/apps-upload' will be broken in isolated environments. Replace with a relative link.
Line 103, Column 87: [Suggestion-disallowed-html-tag] HTML tag 'TeamsAppDownloadPath' isn't allowed. Disallowed HTML poses a security risk and must be replaced with approved Docs Markdown syntax.
Line 104, Column 109: [Suggestion-disallowed-html-tag] HTML tag 'ActionPackageDownloadPath' isn't allowed. Disallowed HTML poses a security risk and must be replaced with approved Docs Markdown syntax.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

repo: MicrosoftDocs/kaizala-docs


text:
Daisyfeller

Please use this template to ensure easier processing of your pull request
Category

[ x] Content fix
[ ] New article

Docs Build status updates of commit e42b8a1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Community/managing-external-guest-in-SharePoint-vs-Teams.md
:bulb:Suggestion
View
Details

Community/list-column-or-site-column-which-one-to-choose.md
:white_check_mark:Succeeded
View

Community/microsoft365-maturity-model--business-process.md
:white_check_mark:Succeeded
View

Community/microsoft365-maturity-model--communication.md
:white_check_mark:Succeeded
View

Community/microsoft365-maturity-model--customization-and-development.md
:white_check_mark:Succeeded
View

Community/microsoft365-maturity-model--how-to-elevate-collaboration.md
:white_check_mark:Succeeded
View

Community/microsoft365-maturity-model--how-to-elevate-communication.md
:white_check_mark:Succeeded
View

Community/managing-external-guest-in-SharePoint-vs-Teams.md

Line 63, Column 5: [Suggestion: duplicate-alt-text - See documentation] Alt text 'guest' is duplicated. Within an article, alt text must be unique.
Line 64, Column 5: [Suggestion: duplicate-alt-text - See documentation] Alt text 'guest' is duplicated. Within an article, alt text must be unique.
Line 124, Column 3: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /microsoft-365/admin/create-groups/manage-guest-access-in-groups?view=o365-worldwide#block-guest-users-from-a-specific-group. Otherwise, remove the view parameter.
Line 128, Column 3: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /office365/admin/create-groups/manage-guest-access-in-groups?view=o365-worldwide. Otherwise, remove the view parameter.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 4d04a50:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Community/list-column-or-site-column-which-one-to-choose.md
:white_check_mark:Succeeded
View

Community/managing-external-guest-in-SharePoint-vs-Teams.md
:white_check_mark:Succeeded
View

Community/microsoft365-maturity-model--business-process.md
:white_check_mark:Succeeded
View

Community/microsoft365-maturity-model--communication.md
:white_check_mark:Succeeded
View

Community/microsoft365-maturity-model--customization-and-development.md
:white_check_mark:Succeeded
View

Community/microsoft365-maturity-model--how-to-elevate-collaboration.md
:white_check_mark:Succeeded
View

Community/microsoft365-maturity-model--how-to-elevate-communication.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 4d04a50:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Community/list-column-or-site-column-which-one-to-choose.md
:white_check_mark:Succeeded
View

Community/managing-external-guest-in-SharePoint-vs-Teams.md
:white_check_mark:Succeeded
View

Community/microsoft365-maturity-model--business-process.md
:white_check_mark:Succeeded
View

Community/microsoft365-maturity-model--communication.md
:white_check_mark:Succeeded
View

Community/microsoft365-maturity-model--customization-and-development.md
:white_check_mark:Succeeded
View

Community/microsoft365-maturity-model--how-to-elevate-collaboration.md
:white_check_mark:Succeeded
View

Community/microsoft365-maturity-model--how-to-elevate-communication.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


text:
Microsoft Viva

The table is missing the data locations for Microsoft Viva

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 61c6fa7b-7e9e-21a5-40da-adbd35040ec1
Version Independent ID: 530df3b2-2048-8351-2f09-59e604aedf5b
Content: Microsoft 365 data locations - Microsoft 365 Enterprise
Content Source: microsoft-365/enterprise/o365-data-locations.md
Service: o365-solutions
GitHub Login: @dmwmsft
Microsoft Alias: deanw

@lkchild Thank you for your feedback. I'm working with the author and will update this shortly.
Thanks
Sri

authors: lkchild msbemba


text:
Creating modern template from Word doc exceptions

As a Syntax user, I want to create a modern template with placeholders in tables so that I can use already existing Word templates and not spend time creating new ones.
Under Create a modern template section, at the end of number 5, please add (or a note to this effect):

[!NOTE] You cannot add placeholders within a table.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ab6e35ec-e5f9-d97f-64c6-f0637f3aef09
Version Independent ID: ab6e35ec-e5f9-d97f-64c6-f0637f3aef09
Content: Create documents using content assembly in Microsoft SharePoint Syntex
Content Source: microsoft-365/contentunderstanding/content-assembly.md
Product: microsoft-365-enterprise
GitHub Login: @chuckedmonson
Microsoft Alias: chucked

Thank you for the feedback. We are looking into it and will let you know.

Updated content accordingly. Thank you for your suggestion.

Hello,
Just for clarification, the update does not indicate that text placeholders are not allowable in tables. Please reopen.

@oliviadudley -- Thank you for the follow up. It says that tables aren't supported (thereby placeholders in tables are not supported. Do you think that needs to be clearer? Thank you.

authors: chuckedmonson oliviadudley


text:
Update turn-off-directory-synchronization.md

Added groups as well
Fixes https://github.com/MicrosoftDocs/microsoft-365-docs/issues/13195

@JohanFreelancer9 Please copy review

@kelleyvice-msft Please merge this PR. Thanks

authors: msbemba yogkumgit


text:
Update compliance-manager-mcca.md

Fixed a typo on line 27.

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks


text:
Creating .MSIX package from Visual Studio on Windows 8.1

I cannot find anywhere on the internet information on how one actually creates a .MSIX package in a Windows 8.1 development environment (WPF .NET Core on VS 2019). Seeing as MSIX Core is for deployment in such an environment, don't you think it's conceivable that the dev may also be done in Windows 8.1? Every tutorial out there assumes Windows 10 as the dev environment.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 37eced72-23b9-9555-6388-38b996277863
Version Independent ID: 2d144a55-69a9-b4fe-8891-78a2f72b20d8
Content: MSIX Core - MSIX
Content Source: msix-src/msix-core/msixcore.md
Product: msix
GitHub Login: @dianmsft
Microsoft Alias: diahar

Hi @RoyceLithgo
If you're using VS 2019 you can package your app as an MSIX on Windows 8.1. You'll need to make sure you have the UWP workload installed, it's required for MSIX packaging and you can get it by running the VS installer.
The only caveat is that you won't be able to debug the app (F5) for testing as the required APIs to debug the MSIX package are not available on Windows 8.1.
Tanaka (MSFT)

authors: Huios RoyceLithgo

repo: MicrosoftDocs/msix-docs


text:
Configure Azure Pipelines

This pipeline configuration builds the application and produces a build for the Release configuration.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: LokeshVarman sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

authors: LokeshVarman msftclas


text:
Update teams-together-mode.md

Correcting spelling of word in step 15.

Acrolinx Scorecards
We do not currently enforce a minimum score for content merged to the default branch. This will change in the future.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/apps-in-teams-meetings/teams-together-mode.md
90
26
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit fef7295:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/apps-in-teams-meetings/teams-together-mode.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

repo: MicrosoftDocs/msteams-docs


text:
Live

Test PR

Docs Build status updates of commit 49cff75:
:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Test PR


text:
-FilterConditons section the example and PowerShell do not match

The text states

User or Group: Active Directory attributes. For example, for the condition "('Country or region' equals 'US' or 'Canada') and 'Department' equals 'Finance'", use the following syntax: @{"Conditions" = @(@{"Conditions" = @(@{"Value" = "US"; "Operator" = "Equals"; "Name" = "CountryOrRegion"}, @{"Value" = "CA"; "Operator" = "Equals"; "Name" = "CountryOrRegion"}); "Conjunction" = "Or"}, @{"Value" = "Finance"; "Operator" = "NotEquals"; "Name" = "Department"}); "Conjunction" = "And"}

The correct PowerShell is
@{"Conditions" = @(@{"Conditions" = @(@{"Value" = "US"; "Operator" = "Equals"; "Name" = "CountryOrRegion"}, @{"Value" = "Canada"; "Operator" = "Equals"; "Name" = "CountryOrRegion"}); "Conjunction" = "Or"}, @{"Value" = "Finance"; "Operator" = "Equals"; "Name" = "Department"}); "Conjunction" = "And"}

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: f296664a-de4a-4045-17a0-9a7b50b7980d
Version Independent ID: 9d9b1cdf-ae45-0565-30b2-13266c29f6b7
Content: Set-AdaptiveScope (ExchangePowerShell)
Content Source: exchange/exchange-ps/exchange/Set-AdaptiveScope.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@nikki-c, fixed in both New-AdaptiveScope and Set-AdaptiveScope.
Thanks for the feedback.
Closing.

authors: chrisda nikki-c

repo: MicrosoftDocs/office-docs-powershell


text:
new_shell

[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: c7f835af-5905-368a-df68-6646782ad807
Version Independent ID: 153ce2d2-dab5-9c8f-c511-ee3bc8ee2dbc
Content: Set-Mailbox (ExchangePowerShell)
Content Source: exchange/exchange-ps/exchange/Set-Mailbox.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@WatchTower001110, is there a question in there somewhere? Are you asking about the vast number of parameter sets (a.k.a. syntax blocks) in Set-Mailbox?


text:
Azure Automation - Unable to load "ieframe.dll"

I've deployed the 4.0.0 MicrosoftTeams powershell module to Azure Automation, and have written a RunBook to assign a policy to a teams user to be used as part of our onboarding process. However, when running the playbook on Azure I'm getting the following error,
Connect-MicrosoftTeams : Unable to load DLL 'IEFRAME.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E) At line:15 char:1 + Connect-MicrosoftTeams -Credential $credential + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : AuthenticationError: (:) [Connect-MicrosoftTeams], DllNotFoundException + FullyQualifiedErrorId : Connect-MicrosoftTeams,Microsoft.TeamsCmdlets.Powershell.Connect.ConnectMicrosoftTeams
None of the documentation specifies that this module isn't compatible with being Run without a hybrid worker.
Can someone clarify if this should be working / is an issue, or if its just not documented that a hybrid worker is required please?

@madshaun1984 - thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome, let me know if it can be called out in the docs.
Please follow this link to contact support for business products: https://docs.microsoft.com/office365/admin/contact-support-for-business-products.
Please keep us posted here on the resolution to feed whatever information you discover into the content.

@dariomws Thank you very much for the contribution and sharing this explanation. @madshaun1984 Hope this comment is helpful for you. Considering the nature of the issue, as advised, please open a service ticket in your tenant and follow with them for the resolution. We proceed to close it as here we are limited to documentation fixes and improvements only.
We will be very happy if you can share the outcome or resolution with us if you see documentation update is required. We will certainly update this documentation with that valuable information. Thanks again, for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

authors: dariomws madshaun1984 yogkumgit


text:
Adding acceptable value for Visibility

https://github.com/MicrosoftDocs/office-docs-powershell/issues/4956

Docs Build status updates of commit 98b0d53:
:clock10: Full build: the average full build time is 12 min(s) 13 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 98b0d53:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

teams/teams-ps/teams/Get-Team.md
:white_check_mark:Succeeded
View (teams-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit e64ce93:
:clock10: Full build: the average full build time is 12 min(s) 13 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit e64ce93:
:warning: Validation status: warnings

File
Status
Preview URL
Details

sharepoint/docs-conceptual/sharepoint-online/connect-sharepoint-online.md
:warning:Warning
View (sharepoint-ps)
Details

teams/teams-ps/teams/Get-Team.md
:white_check_mark:Succeeded
View (teams-ps)

sharepoint/docs-conceptual/sharepoint-online/connect-sharepoint-online.md

[Warning] Text in the first line of Note/Section/Video is not valid. Will be rendererd to <blockquote>

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Added PR https://github.com/MicrosoftDocs/office-docs-powershell/pull/4965 to fix warning unrelated to this PR.

Docs Build status updates of commit d88a6d6:
:clock10: Full build: the average full build time is 12 min(s) 13 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit d88a6d6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

teams/teams-ps/teams/Get-Team.md
:white_check_mark:Succeeded
View (teams-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


text:
Update Set-CsTenantNetworkSite.md

remove "SiteAddress"

Docs Build status updates of commit 4515237:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Set-CsTenantNetworkSite.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 489b137:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Set-CsTenantNetworkSite.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


text:
Fix example

closes https://github.com/MicrosoftDocs/office-docs-powershell/issues/8195

Docs Build status updates of commit 0746657:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-server/Add-SPClaimTypeMapping.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@tseward

@tiburd Please merge this PR. Thanks

Docs Build status updates of commit b919c91:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-server/Add-SPClaimTypeMapping.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


text:
Extended SpamFilteringEnabledType Description

Added extended description for SpamFilteringEnabledType parameter

Docs Build status updates of commit f035595:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Hello @YuriySamorodov thanks for your contribution, as you might know, this is somewhat difficult to test, can you tell us how you were able to test this? Thank you

These details have been provided by Microsoft Support (Ticket 27190817) and @dinabogdan

Docs Build status updates of commit 89c0fca:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit c01559a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@dinabogdan, Could you kindly confirm this information? Thanks!

Docs Build status updates of commit 86ccfe8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@tiburd Kindly take a suitable action. Thanks

Hi! Sorry for so delayed response. Indeed, I have discussed with @YuriySamorodov offline :) Thanks!

Docs Build status updates of commit 4c554bd:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Set-CsTeamsCallingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel