text:
Update limits-specifications-teams.md

https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/5103
Added note.

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@nej-nej please review this PR and let us know whether it's OK to merge.

Adding @Gauravmailto:Gaurav.Pancholi@microsoft.com/ @Namendramailto:Namendra.Kumar@microsoft.com, can you please let us know if this is correct ?
This is a PR to update the user facing docs: https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/pull/5269/files
From: Manuela Scanu notifications@github.com
Sent: Friday, July 10, 2020 6:31 AM
To: MicrosoftDocs/OfficeDocs-SkypeForBusiness OfficeDocs-SkypeForBusiness@noreply.github.com
Cc: Neeraj Jain nej@microsoft.com; Assign assign@noreply.github.com
Subject: Re: [MicrosoftDocs/OfficeDocs-SkypeForBusiness] Update limits-specifications-teams.md (#5269)
Assigned #5269https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FOfficeDocs-SkypeForBusiness%2Fpull%2F5269&data=02|01|nej%40microsoft.com|a9aff9bec3a04b02941708d8248a1205|72f988bf86f141af91ab2d7cd011db47|1|0|637299522718660200&sdata=9o%2B3Pa5mIdiamqlEyQG2RJhUnw%2B0J0JdFr%2Fqx7IBZlQ%3D&reserved=0 to @nej-nejhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnej-nej&data=02|01|nej%40microsoft.com|a9aff9bec3a04b02941708d8248a1205|72f988bf86f141af91ab2d7cd011db47|1|0|637299522718670192&sdata=usa6f73RGCPCBD0A5aaPBqQjyfjbw%2BIjUpot5Tgr%2F0w%3D&reserved=0.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FOfficeDocs-SkypeForBusiness%2Fpull%2F5269%23event-3532307039&data=02|01|nej%40microsoft.com|a9aff9bec3a04b02941708d8248a1205|72f988bf86f141af91ab2d7cd011db47|1|0|637299522718670192&sdata=ijZd91FJX8B1M5V7ze7K%2BdFpQQP1hLpnGrV0OeTekAg%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANFYSM6YI5J7DMWOZA33MSDR22KQ3ANCNFSM4OOZRNCQ&data=02|01|nej%40microsoft.com|a9aff9bec3a04b02941708d8248a1205|72f988bf86f141af91ab2d7cd011db47|1|0|637299522718670192&sdata=mglGkPgIyA9wDwvDNPPyes8gSaK1PblhGRX1VSfwJBI%3D&reserved=0.

@Neerajmailto:nej@microsoft.com - The meeting expiration section in this doc correctly describes the expiration time: https://docs.microsoft.com/en-us/microsoftteams/limits-specifications-teams
From: Neeraj Jain nej@microsoft.com
Sent: Friday, July 10, 2020 5:22 AM
To: MicrosoftDocs/OfficeDocs-SkypeForBusiness reply@reply.github.com; MicrosoftDocs/OfficeDocs-SkypeForBusiness OfficeDocs-SkypeForBusiness@noreply.github.com; Gaurav Pancholi Gaurav.Pancholi@microsoft.com; Namendra Kumar Namendra.Kumar@microsoft.com
Cc: Assign assign@noreply.github.com
Subject: RE: [MicrosoftDocs/OfficeDocs-SkypeForBusiness] Update limits-specifications-teams.md (#5269)
Adding @Gauravmailto:Gaurav.Pancholi@microsoft.com/ @Namendramailto:Namendra.Kumar@microsoft.com, can you please let us know if this is correct ?
This is a PR to update the user facing docs: https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/pull/5269/fileshttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FOfficeDocs-SkypeForBusiness%2Fpull%2F5269%2Ffiles&data=04|01|Gaurav.Pancholi%40microsoft.com|6fcab24af24b41f6040008d824cbea4f|72f988bf86f141af91ab2d7cd011db47|0|0|637299805575167342|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=gD5qaL%2FsS4NRxnQ5c39yPH7fRnmsde2IvqH8CjDKRew%3D&reserved=0
From: Manuela Scanu <notifications@github.commailto:notifications@github.com>
Sent: Friday, July 10, 2020 6:31 AM
To: MicrosoftDocs/OfficeDocs-SkypeForBusiness <OfficeDocs-SkypeForBusiness@noreply.github.commailto:OfficeDocs-SkypeForBusiness@noreply.github.com>
Cc: Neeraj Jain <nej@microsoft.commailto:nej@microsoft.com>; Assign <assign@noreply.github.commailto:assign@noreply.github.com>
Subject: Re: [MicrosoftDocs/OfficeDocs-SkypeForBusiness] Update limits-specifications-teams.md (#5269)
Assigned #5269https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FOfficeDocs-SkypeForBusiness%2Fpull%2F5269&data=04|01|Gaurav.Pancholi%40microsoft.com|6fcab24af24b41f6040008d824cbea4f|72f988bf86f141af91ab2d7cd011db47|0|0|637299805575167342|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=qOACL8l%2BMY%2FWt6Bf4PjznDYNYaEQ7XQox8p5IIVs%2FY8%3D&reserved=0 to @nej-nejhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnej-nej&data=04|01|Gaurav.Pancholi%40microsoft.com|6fcab24af24b41f6040008d824cbea4f|72f988bf86f141af91ab2d7cd011db47|0|0|637299805575177298|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=wU8gOyGKLmx2Kmv0Gw1qcyVfZxScgU4%2B1o6yK%2FXpXLQ%3D&reserved=0.

You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FOfficeDocs-SkypeForBusiness%2Fpull%2F5269%23event-3532307039&data=04|01|Gaurav.Pancholi%40microsoft.com|6fcab24af24b41f6040008d824cbea4f|72f988bf86f141af91ab2d7cd011db47|0|0|637299805575177298|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=%2F6R8tsHJh2hh6tC7GkjiOuHFhQfSnxcCVoNFv2sDWpI%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANFYSM6YI5J7DMWOZA33MSDR22KQ3ANCNFSM4OOZRNCQ&data=04|01|Gaurav.Pancholi%40microsoft.com|6fcab24af24b41f6040008d824cbea4f|72f988bf86f141af91ab2d7cd011db47|0|0|637299805575187254|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=k5N9TbVY%2FN9ztxRnXDPUgRCgcsJBRjvokKs%2FTFgHlG0%3D&reserved=0.

Merging per @nej-nej @Gaurav0327

authors: LolaJacobsen lindspea nej-nej scanum


text:
Update chat in meeting in meeting-policies-in-teams.md

Closes https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/9452.

Learn Build status updates of commit dd82d14:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Teams/meeting-policies-in-teams.md
:white_check_mark:Succeeded

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 learn.microsoft.com contributor guidesPost your question in the Learn support channel

@tonysmit
PR has been copyedited and is ready for final review, could you please check and merge? Thanks!

@tonysmit
PR has been copyedited and is ready for final review, could you please check and merge? Thanks!

@CarolynRowe
PR has been copyedited and is ready for final review, could you please check and merge? Thanks!

source: gharchive/pull-request

authors: dariomws opbld33 scanum

license_type: permissive

license_source: github-api


text:
1710 to 1902 upgrade is not supported remove it from https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/whats-new-in-version-1902

https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/whats-new-in-version-1902
"Apply this update on sites that run version 1710, 1802, 1806, or 1810. When installing a new site, it's also available as a baseline version. "
Remove 1710 as 1710 to 1902 Upgrade is not supported. Supported scenario:
1810 --> 1902
1806 --> 1902
1802 --> 1902
2012 R2 SP1 /SP2 à 1902 (the only CD support)

@suchouh Thanks for noticing this!

source: gharchive/issue

authors: mestew suchouh

repo: MicrosoftDocs/SCCMdocs


text:
Azure Functions v2 instead of Web Jobs

Background jobs
https://github.com/microsoftdocs/architecture-center/blob/master/docs/best-practices/background-jobs.md
I think this article should be updated to use Azure Functions v2 in the example.
As of today, Azure Functions v2(Durable Functions) is a recommended solution for Background jobs in Azure.

Hi @thara0402  Thanks for reaching out. We are actively investigating and will get back to you shortly

Agree! Closing as a dup of #1361

authors: DixitArora-MSFT MikeWasson thara0402

repo: MicrosoftDocs/architecture-center


text:
Update hub-spoke.md

Typo correction

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

Verified the update; merging.
@jpalo Thank you for making that fix.

authors: PRMerger6 jpalo ktoliver


text:
Adding a Note: After the Final Migration to Flexible Server, the Source Single Server Will Be Shut Down, Rollback Will Not Be Possible, and Deletion Will Be Irreversible—Applicable to Server Recovery in this Document

Adding a note- After the final migration to Flexible Server, the source Single Server will be shut down, and rolling back from Flexible Server to Single Server will not be possible. Additionally, once the Single Server is deleted, it cannot be recovered. Which is applicable in this doc which refer to server recovery.

@code-sidd
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

Hi @Court72 , any update on this as well?

I sent a Teams message to the author today.

#assign @varun-dhawan

@kabharati, @varun-dhawan
@
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.

@shriram-muthukrishnan  to confirm

@Court72 just checking to see an updates.

authors: Court72 code-sidd kabharati rarandiv

repo: MicrosoftDocs/azure-databases-docs


text:
VSTest and MSBuild: document enableDefaultLogger parameter

https://github.com/microsoft/azure-pipelines-tasks/pull/14331 added an enableDefaultLogger parameter to the VSBuild tasks, but it's not mentioned here.
cc @anatolybolshakov who made the change.

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

ID: 29f86c97-f534-50ad-bfb1-a2cf78c7af94
Version Independent ID: acea40e3-512b-4d9a-9389-71b8b24327be
Content: Visual Studio Build build and release task - Azure Pipelines
Content Source: docs/pipelines/tasks/build/visual-studio-build.md
Product: devops
Technology: devops-cicd-tasks
GitHub Login: @vijayma
Microsoft Alias: vijayma

Thanks for letting us know. This issue is fixed in our new task reference, which is generated using the task source code and includes all task inputs, including any aliases here:
https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/vsbuild-v1?view=azure-pipelines
Please check it out and let us know what you think. Thank you.

repo: MicrosoftDocs/azure-devops-docs


text:
documentation mentions 2 npmrc files in the "project setup section", but only refers to one npmrc file in the "credentials setup section". Don't know which npmrc file to modify in the "credentials setup" section

[Enter feedback here]

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

ID: 4a25fb7f-d07f-f92e-55db-a44d41bd6e51
Version Independent ID: 63828151-7f31-7abc-7a52-c4538815e368
Content: Set up your client's npmrc - Azure Artifacts
Content Source: docs/artifacts/npm/npmrc.md
Product: devops
Technology: devops-artifacts
GitHub Login: @ramiMSFT
Microsoft Alias: rabououn

@changc42 Thanks for your question. While we look into changes for the article, consider these resources:

Azure DevOps Services
Azure DevOps on Stack Overflow

@changc42 The second .npmrc file should be kept locally in your home directory. This one should contain all your credentials. I'm updating the article shortly.

authors: TimShererWithAquent changc42 ramiMSFT


text:
PowerBI error

Hi,
I'm trying to run the query for test execution status of requirements and getting the following error:
DataSource.Error: OData: The property 'ParentWorkItemTitle' does not exist on type 'Microsoft.VisualStudio.Services.Analytics.Model.TestPoint'. Make sure to only use property names that are defined by the type or mark the type as open type.
Details:
DataSourceKind=OData
DataSourcePath=https://analytics.dev.azure.com/{org}/{project}/_odata/v3.0-preview/TestPoints
Any idea? I'm using PowerBI Desktop version 2.80.5803.641 64-bit (April 2020)
Thanks.

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

ID: 40bb3182-6622-0d21-31d8-db6db932cc8d
Version Independent ID: 868c0e69-6528-a5d7-10f5-c0b384bc9310
Content: Requirements tracking, Stories overview rollup report - Azure DevOps
Content Source: docs/report/powerbi/sample-stories-overview-rollup.md
Product: devops
Technology: devops-analytics
GitHub Login: @KathrynEE
Microsoft Alias: shdalv

Thanks for your question. It looks like you're working through an issue with your scenario or implementation, rather than an issue with the documentation. Here are a couple of options where you might consider asking your question:

Azure DevOps Support Bot
Azure DevOps on Stack Overflow

Thanks for the reply. I did copy / paste the PowerBI query in the documentation in the PowerBI query editor and got that error. I know it might a PowerBI issue, but I assumed the query was tested in PowerBI before being added to the documentation.
Thank you

@ivee-tech -- Dan, thank you for clarifying.
@KathrynEE -- Kathryn, please look into this issue.

@ivee-tech, sorry for the delayed response, but the property ParentWorkItemTitle doesn't exist on the TestPoint entity. What is the query that you are trying to run? In the query from documentation -

@ivee-tech - I'm closing this issue as there appears to be a response from Qshaaradmsft and no reply to their query. If you need to reopen it, please do so and provide more context or response to the query.

Hi Everyone,
Sorry for the delay; it's all good now, the issue has been fixed.
Kind Regards,Dan    On Saturday, August 29, 2020, 10:54:15 AM GMT+10, KathrynEE notifications@github.com wrote:
@ivee-tech - I'm closing this issue as there appears to be a response from Qshaaradmsft and no reply to their query. If you need to reopen it, please do so and provide more context or response to the query.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

authors: KathrynEE WilliamAntonRohm ivee-tech shaaradmsft


text:
VSBuild task ignores DacApplicationName and SqlTargetName properties

I have sqlproj with DacApplicationName and SqlTargetName set up to "CDB_Acquiring". But VSBuild task ignore it and use project name as output for .dacpac:
Project "D:\a\1\s\Acquiring\MySolution.sln" (1) is building "D:\a\1\s\Acquiring\MySolution.DB\MySolution.DB.sqlproj" (7) on node 1 (default targets).
PrepareForBuild:
  Creating directory "bin\Release\".
CoreCompile:
  C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin\Roslyn\csc.exe /noconfig /nowarn:1701,1702 /nostdlib+ /errorreport:prompt /warn:4 /define:TRACE /highentropyva+ /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\mscorlib.dll" /debug:pdbonly /optimize+ /out:obj\Release\MySolution.DB.dll /ruleset:"C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Team Tools\Static Analysis Tools\\Rule Sets\MinimumRecommendedRules.ruleset" /subsystemversion:6.00 /target:library /warnaserror- /utf8output "C:\Users\VssAdministrator\AppData\Local\Temp\.NETFramework,Version=v4.5.2.SqlClrAttributes.cs"
  Using shared compilation with compiler from directory: C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin\Roslyn
SqlBuild:
  Creating a model to represent the project...
  Loading project references...
  Loading project files...
  Building the project model and resolving object interdependencies...
  Validating the project model...
  Writing model to D:\a\1\s\Acquiring\MySolution.DB\obj\Release\Model.xml...
  Writing create script to MySolution.DB_Create.sql...
CopyFilesToOutputDirectory:
  Copying file from "obj\Release\MySolution.DB.dll" to "bin\Release\MySolution.DB.dll".
  MySolution.DB -> D:\a\1\s\Acquiring\MySolution.DB\bin\Release\MySolution.DB.dll
  Copying file from "obj\Release\MySolution.DB.pdb" to "bin\Release\MySolution.DB.pdb".
SqlPrepareForRun:
  MySolution.DB -> D:\a\1\s\Acquiring\MySolution.DB\bin\Release\MySolution.DB.dacpac

My task is:
- task: VSBuild@1
      inputs:
        msbuildArgs: '/p:IsPackaging=true'
        clean: true
        solution: '$(Build.Repository.Name)\**\*.sln'
        platform: ${{ variables.platform }}
        configuration: ${{ variables.configuration }}

As you can see there is clean: true, but even with clean this doesn't work. I spent huge amount of time for determine the reason, but without success.

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

ID: 29f86c97-f534-50ad-bfb1-a2cf78c7af94
Version Independent ID: acea40e3-512b-4d9a-9389-71b8b24327be
Content: Visual Studio Build build and release task - Azure Pipelines
Content Source: docs/pipelines/tasks/build/visual-studio-build.md
Product: devops
Technology: devops-cicd-tasks
GitHub Login: @vijayma
Microsoft Alias: vijayma

Problem was with .sqlproj file that missed DacApplicationName and SqlTargetName properties for 'Release' configuration. I had to set up this manually for both configs.


text:
The steps "Update the zypper package index and install" should be updated

Running the indicated commnad in Suse Enterprise Server 12 fails.
As per the following post https://github.com/Azure/azure-cli/issues/9665#issuecomment-535304323 the new step is:

Remove the -y option when install:
sudo zypper install --from azure-cli azure-cli
then input 2 to continue install.

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

ID: 26961ab6-af63-1bb9-53d1-566e4acc2896
Version Independent ID: 2c26a785-ca52-321a-ba33-4622ed9d37a2
Content: Install the Azure CLI on Linux with zypper
Content Source: docs-ref-conceptual/install-azure-cli-zypper.md
Service: azure-cli
GitHub Login: @dbradish-microsoft
Microsoft Alias: dbradish

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

@alextuncu Thank you for bringing this to our attention! I have submitted a PR to fix the issue, the change is awaiting review and will reflect once merged.

@alextuncu We will now proceed to close this thread as resolved, but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

authors: BhargaviAnnadevara-MSFT alextuncu

repo: MicrosoftDocs/azure-docs-cli


text:
Export Secret does not work on Azure Cloud Shell

The provided code does not work on Azure Cloud Shell.
Azure:/
PS Azure:\> $BSTR = [System.Runtime.InteropServices.Marshal]::SecureStringToBSTR($sp.Secret)
Exception calling "SecureStringToBSTR" with "1" argument(s): "Value cannot be null.
Parameter name: s"
At line:1 char:1
+ $BSTR = [System.Runtime.InteropServices.Marshal]::SecureStringToBSTR( ...
+ CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : ArgumentNullException

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

ID: 7dd724a1-cf89-45b8-85d6-e9bb815dde0c
Version Independent ID: 84b2cbcb-1f11-9a6d-23fd-5c8d76453fa8
Content: Use Azure service principals with Azure PowerShell
Content Source: docs-conceptual/azps-2.7.0/create-azure-service-principal-azureps.md
GitHub Login: @sptramer
Microsoft Alias: sttramer

Disregard, forgot to assign to $sp :)

repo: MicrosoftDocs/azure-docs-powershell


text:
Docs.MS Release Updates for azure_template

not-specified

Docs Build status updates of commit 16b4400:
:clock10: Full build: the average full build time is 155 min(s) 59 sec(s), this is based on the last 451 build(s) for this repository.

Docs Build status updates of commit 16b4400:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-services/template-readme.md
:warning:Warning
View (azure-python)
Details

ci-configs/packages-latest.json
:white_check_mark:Succeeded

docs-ref-services/template-readme.md

Line 13: [Warning-h1-not-first] Markdown content is not allowed before {0}.
Line 25: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 29: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 33: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 37: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 41: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 45: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

repo: MicrosoftDocs/azure-docs-sdk-python


text:
recommend time.windows.com also for linux?

Hi,
I got a question, the windows article[1] recommends to use time.windows.com -- should this also be recommended for linux users? It looks like that is a normal ntp server which is hosted in Azure. Or let me put the question differently, is there a reason I shouldn't be using that time server in Azure with chronyd/ntpd?
[1] https://learn.microsoft.com/en-us/azure/virtual-machines/windows/time-sync

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

ID: 8f5e6687-3b97-7f25-5e7b-91265764c816
Version Independent ID: d3f3b17a-a25b-656b-314f-25002c5d5f9f
Content: Time sync for Linux VMs in Azure - Azure Virtual Machines
Content Source: articles/virtual-machines/linux/time-sync.md
Service: virtual-machines
GitHub Login: @cynthn
Microsoft Alias: cynthn

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

Hi @Klaas-
Could you please refer to the below links for your query. It can be helpful.
https://learn.microsoft.com/en-us/azure/virtual-machines/linux/time-sync#:~:text=On Ubuntu 19.10,the following statement%3A
Disclaimer: This response contains a reference to a third-party World Wide Web site. Microsoft is providing this information as convenient to you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there.
https://chrony.tuxfamily.org/

Hi @AjayBathini-MSFT
I think you misunderstood my question, the windows article:
https://github.com/MicrosoftDocs/azure-docs/blame/main/articles/virtual-machines/windows/time-sync.md#L49
recommends time.windows.com as ntp server
the Linux document suggests to use ntp public pool and/or PTP
https://github.com/MicrosoftDocs/azure-docs/blame/main/articles/virtual-machines/linux/time-sync.md#L52
I am asking, why don't you say use time.windows.com instead of the public ntp pools? Then the ntp server would be inside azure, looks to be a anycast service :)
Greetings
Klaas

Hi @Klaas-
Thank you for your feedback!
Since this issue isn't directly related to improving our docs, and to gain a better understanding of your issue, I'd recommend working closer with our support team via an [Azure support request] (https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request). Or you can leverage our Q&A forum by posting your issue there so our community, and MVPs can further assist you in troubleshooting this issue or finding potential workarounds.
[Teams Q&A forum] (https://docs.microsoft.com/en-us/answers/topics/46488/office-teams-windows-itpro.html) for technical questions about the configuration and administration of Microsoft Teams on Windows.
[Microsoft Teams Community forum] (https://answers.microsoft.com/en-us/msteams/forum?sort=LastReplyDate&dir=Desc&tab=All&status=all&mod=&modAge=&advFil=&postedAfter=&postedBefore=&threadType=All&isFilterExpanded=false&page=1)
Thank you for your time and patience throughout this issue.

I will transform this into a support case.

authors: AjayBathini-MSFT Klaas- YashikaTyagii

repo: MicrosoftDocs/azure-docs


text:
Link broken

The link is broken for (Microsoft.Azure.Extensions.CustomScript) . Also, maybe add the context in which the script would be running. Like will it have sudo privilleges? If yes, which user account does it use?

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

ID: ec45418f-2503-415d-12c1-3165be164c69
Version Independent ID: fc84467e-16a7-33ab-1511-7df7fa48a512
Content: Run custom scripts on Linux VMs in Azure
Content Source: articles/virtual-machines/extensions/custom-script-linuxOstc.md
Service: virtual-machines-linux
GitHub Login: @danielsollondon
Microsoft Alias: danis

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

@blueelvis I have fixed the link. The changes will go live in a few hours.
I know CSE for windows will run at a admin level so I assume that linux does the same.
I will assign to the content author to review and see if we should add that tip to the doc.
@danielsollondon can you take a look?

authors: MicahMcKittrick-MSFT blueelvis


text:
FRA creation

For the step where FRA is created, you must also select "External (None)"  for "Redundancy" option.
Thanks
Cenk Ersoy

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

ID: 2919d2c7-ca01-8d15-3f8b-1a46d4b19b66
Version Independent ID: 799db1e8-bea0-5188-c1b2-482fa3cf2533
Content: Set up Oracle ASM on an Azure Linux virtual machine - Azure Virtual Machines
Content Source: articles/virtual-machines/workloads/oracle/configure-oracle-asm.md
Service: virtual-machines
Sub-service: oracle
GitHub Login: @jjaygbay1
Microsoft Alias: jacobjaygbay

@cenk-ersoy
Thanks for your feedback! We will investigate and update as appropriate.

@cenk-ersoy
Thanks for reporting this! We have created a PR for this issue and the changes should go live soon.
https://github.com/MicrosoftDocs/azure-docs-pr/pull/248825

authors: AjayBathini-MSFT cenk-ersoy


text:
Clarification on vnet and subnets for private web auth workspace.

Very thorough and excellent documentation, thank you! Under "Step 4: Create a private endpoint to support SSO for web browser access," it doesn't seem possible to create a web authentication workspace without also creating public and private subnets for it, even though these subnets will not be used. It's probably possible to provision the workspace and then later go into the virtual network settings and delete the subnets after they have been created, but this pre-supposes that the virtual network has enough spare IP address space to begin with. Many corporate vnets won't.
Also, this section says to "Create or use a VNet separate from the VNet that you use for your main workspace VNet" for the web auth workspace. This contradicts the rationale for enabling the private link as a simplified deployment, which is that having a separate VNET may not be feasible.
Finally, under the "Authentication troubleshooting" section, for the “Configured privacy settings disallow access for workspace...” error, the suggestion that "you are connecting to the workspace over the public internet (not from a private link connection)" could perhaps be elaborated on to explain how to know if this is the case. For example, the user should probably do an nslookup of the workspace URL, and if it resolves to a public IP address, to try temporarily overriding the DNS using the etc/hosts file.

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

ID: 507faeeb-1335-b6dd-ed5e-1f3c091f124e
Version Independent ID: 507faeeb-1335-b6dd-ed5e-1f3c091f124e
Content: Enable Azure Private Link as a simplified deployment - Azure Databricks
Content Source: databricks/administration-guide/cloud-configurations/azure/private-link-simplified.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

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

Powered by Citizen
On Tue, Oct 10, 2023 at 4:21 PM Kevin Davis @.***>
wrote:

Very thorough and excellent documentation, thank you! Under "Step 4:
Create a private endpoint to support SSO for web browser access," it
doesn't seem possible to create a web authentication workspace without also
creating public and private subnets for it, even though these subnets will
not be used. It's probably possible to provision the workspace and then
later go into the virtual network settings and delete the subnets after
they have been created, but this pre-supposes that the virtual network has
enough spare IP address space to begin with. Many corporate vnets won't.
Also, this section says to "Create or use a VNet separate from the VNet
that you use for your main workspace VNet" for the web auth workspace. This
contradicts the rationale for enabling the private link as a simplified
deployment, which is that having a separate VNET may not be feasible.
Finally, under the "Authentication troubleshooting" section, for the
“Configured privacy settings disallow access for workspace...” error, the
suggestion that "you are connecting to the workspace over the public
internet (not from a private link connection)" could perhaps be elaborated
on to explain how to know if this is the case. For example, the user should
probably do an nslookup of the workspace URL, and if it resolves to a
public IP address, to try temporarily overriding the DNS using the
etc/hosts file.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com
http://learn.microsoft.com ➟ GitHub issue linking.

ID: 507faeeb-1335-b6dd-ed5e-1f3c091f124e
Version Independent ID: 507faeeb-1335-b6dd-ed5e-1f3c091f124e
Content: Enable Azure Private Link as a simplified deployment -
Azure Databricks
https://learn.microsoft.com/en-us/azure/databricks/administration-guide/cloud-configurations/azure/private-link-simplified
Content Source:
databricks/administration-guide/cloud-configurations/azure/private-link-simplified.md
https://github.com/MicrosoftDocs/databricks-pr/blob/live/databricks/administration-guide/cloud-configurations/azure/private-link-simplified.md
Service: azure-databricks
GitHub Login: @mssaperla https://github.com/mssaperla
Microsoft Alias: saperla

—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/115828, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A6PLA7AP3Y5E2MKDUQVL6R3X6W37DAVCNFSM6AAAAAA527OHYOVHI2DSMVQWIX3LMV43ASLTON2WKOZRHEZTMMRXHAYDCMY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

authors: AjayBathini-MSFT Citizen2023 kevinskii


text:
{regionCode} list should be a webpage not a word document/inaccuracies

The 'Note' for {regionCode} refers users to a URL to download 'AzureRegionCodesList.docx'
This should be available as a webpage so that it is searchable.
In the Government 'Note' the text states

In the above text, {region}

{region} is not used in the Government table.
{region} is only used in the China table.

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

ID: a88af182-32aa-a8f3-359d-b92ae1cfb8c7
Version Independent ID: 01ce07fc-4bc2-def5-9ecd-a80330ad9488
Content: Azure Private Endpoint DNS configuration
Content Source: articles/private-link/private-endpoint-dns.md
Service: private-link
GitHub Login: @asudbring
Microsoft Alias: allensu

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

@bigandyox
Thanks for the feedback!  There is an XML with all of the three letter region codes that Azure Backup uses for private endpoint DNS.  I have put a work item in to add this link to the DNS page and fix the notes.
XML with list of codes.
https://learn.microsoft.com/en-us/azure/backup/scripts/geo-code-list
#please-close

authors: AjayBathini-MSFT asudbring bigandyox


text:
The Backup service can't install backup extension when a VM is not running.

Hi, Team. Recently, one customer in China raised an issue about the following description from this article. The customer believes that the Backup service can’t be able to install backup extension when the VM is not running, and this sentence within this doc will cause the readers' misunderstanding.

After my communication with him, he provided us with some more detailed information that I think may be helpful for you to clarify this point. The following pic shows what clues the customer has collected, just for your reference.

Under this situation, could you please help to confirm whether the description above has the needs to be improved? Thanks in advance.

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

ID: 56186459-5f87-bfa1-fd17-86726298cc62
Version Independent ID: 2e4b94f6-aef9-4d4c-702c-1a1dd0a6769c
Content: Quickstart - Back up a VM with the Azure portal by using Azure Backup - Azure Backup
Content Source: articles/backup/quick-backup-vm-portal.md
Service: backup
GitHub Login: @AbhishekMallick-MS
Microsoft Alias: v-abhmallick

@Johnnytechn Thanks for bring this to our notice. We will discuss this issue with the concerned team and take necessary to steps further.
Just wanted to know regarding the clues that your customer has shared through email. Was that a conversation between your customer and the support professional from Microsoft? If yes, I would request sharing the support request # with us. Thanks!

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

@Johnnytechn Thanks for bringing this to our notice. We will discuss this issue with the concerned team and take necessary steps further.
Just wanted to know regarding the clues that your customer has shared through email. Was that a conversation between your customer and the support professional from Microsoft? If yes, I would request sharing the support request # with us. Thanks!

@Johnnytechn Could you please share more details on this?

Hi, @AbhishekMallick-MS Is there any update?

Hi @Johnnytechn - 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. The requested updates have not been made since the creation of this issue, and the timeline for resolution may vary based on resourcing, so we've created an internal work item to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary. #please-close

authors: AbhishekMallick-MS Johnnytechn SadiqhAhmed-MSFT TPavanBalaji


text:
AKS Learn feedback: Test3

Type of issue
Typo
Feedback
Test3
Page URL
https://review.learn.microsoft.com/en-us/azure/aks/use-managed-identity?branch=pr-en-us-278352#next-steps
Content source URL
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/aks/use-managed-identity.md
Author
@tamram
Document Id
01e98043-dc80-490e-a761-8d558ff4e6df

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

ID: 6a9c74a8-9f1a-3d3d-3aed-f8ec45f92e05
Version Independent ID: 01e98043-dc80-490e-a761-8d558ff4e6df
Content: Use a managed identity in Azure Kubernetes Service (AKS) - Azure Kubernetes Service
Content Source: articles/aks/use-managed-identity.md
Service: azure-kubernetes-service
Sub-service: aks-security
GitHub Login: @tamram
Microsoft Alias: tamram

@JasonWHowell
It looks like your issue is resolved since you closed this thread.
If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.

authors: JasonWHowell TPavanBalaji


text:
Unable to verify certificates

I'm trying to set up a Raspberry Pi 3 as a transparent gateway following this How-to. Everything seems to work until it comes to the verification of certificates.
Testing the connection with openssl leads to "unable to get local issuer certificate" and the following log. The returned error is the same when trying to connect to the IoT Hub instead of the gateway (localhost).
One thing I noticed when inspecting the certs in /etc/ssl/certs is that the filename extension of the CA cert is added twice: "azure-iot-test-only.root.ca.cert.pem.pem". However, I'm not sure if thats relevant. Please tell me if I need to provide any more information.
openssl s_client -connect localhost:8883 -CAfile /home/pi/work/certs/azure-iot-test-only.root.ca.cert.pem -showcerts
CONNECTED(00000003)
depth=2 CN = Test Edge Device CA
verify error:num=20:unable to get local issuer certificate
---
Certificate chain
 0 s:/CN=iotedgegateway
   i:/CN=iotedged workload ca
-----BEGIN CERTIFICATE-----
MIIDwzCCAaugAwIBAgIEOmkVejANBgkqhkiG9w0BAQsFADAfMR0wGwYDVQQDDBRp
b3RlZGdlZCB3b3JrbG9hZCBjYTAeFw0xODA4MTQxNDMxMzhaFw0xODExMTIxNDMw
MzhaMBkxFzAVBgNVBAMMDmlvdGVkZ2VnYXRld2F5MIIBIjANBgkqhkiG9w0BAQEF
AAOCAQ8AMIIBCgKCAQEAvt/im65NNFPOZG2RS2v5CRNvhocLnWU5Q+lx5BqQ1zUD
/5OTiLsPKB7gUI+6SessX/vgfG+phnw70PadhtxAaMV27uSvLFaV/w7A61zrFCw3
EM1yxAjWqgqYzTNWviozQ0I7pfEeTDubY7rqx5Whp2ke+bljIY4+zCTb7BcpBQZk
bt/IX81R05FKZXTwW9EjRujlFwBfTt6Gc1/c0KlgWdnzG8lAxhNLv226gUSXK6am
kkGJuxg0XmMeefKNTBBxCz1Uk3p8K1XUcetdCvJGwhO6Ma7CpquqfV6cDTjHOioK
KznHAXR7Bm19la+CCl6QhkW3twdOUAKiMWrp0qZJ+QIDAQABow0wCzAJBgNVHRME
AjAAMA0GCSqGSIb3DQEBCwUAA4ICAQAcEWVeVMdiVu24YtRD+LqqYjSwjBA4ONJC
7Q7Pw0XMmIpZXhx+zNeV20Wbeqfdw/wWMek76c+Wxo7T+LaacHKD11OeDzghPjoS
o3XLiCWbmk1hYSeUq362ruOEliiTq48f8qcYQM8mnfVPeDUdB/u0LXSDhBw22Zfi
yF/WjvhbfMu2dSxAKn5iPJZUDs2uYTtJG8a+n0nNPOle7gb7QVjy/dCtrXBRkldk
fW0zzvCRfxwZGAjsDxlJhw9NnOu15tLgyQ2hZK8isnqIAwp25qT3YQK4+jYOyZSg
kXc0Lhvr/bE/FuTCGA+YqnUu3hJmHg7tC0CW5qaKUD+4NdRguCXagIIv1oI9yVJ7
KOU2+Rkkc9ht5PMYk2mjcwVI7Tks4j7dy8izVHQiAo/+furMFxqWy9WR5TZ8GRw9
dGgjzL/ayENab0onm15L9GVjMuBXB9PtA1aoODyNOIk0+X2P6OxMEVcwnHmWIqwY
ZcqliiNRokZyG7sr0SXW3zI8R4u2a0nfHxiYgKHbyOiJ7s0VAwXUW4l0Ey6l9kd4
7ZNxwV3nbQ2MsWePRvBnSEl9BLtHts4z/T57TnZOsPfOsfFCPKRaQZNi23umw+0x
cymGKiWwAl5fwpTDQee4s9a6DZGhVHf9HlWiit5+d+1LFQLAZbWT1V0nkyx159QI
zeZAuA7YIw==
-----END CERTIFICATE-----
 1 s:/CN=Test Edge Device CA
   i:/CN=Test Edge Owner CA
-----BEGIN CERTIFICATE-----
MIIEzzCCAregAwIBAgIEMnsjxjANBgkqhkiG9w0BAQsFADAdMRswGQYDVQQDDBJU
ZXN0IEVkZ2UgT3duZXIgQ0EwHhcNMTgwODE0MTQzMDQ0WhcNMTgxMTEyMTQzMDM4
WjAeMRwwGgYDVQQDDBNUZXN0IEVkZ2UgRGV2aWNlIENBMIICIjANBgkqhkiG9w0B
AQEFAAOCAg8AMIICCgKCAgEAyju2mdNAddvZdIbWQNxPciR572tk2tlcb1UiHY0S
Tlt5e7mNDpbA5+KkspsYnSkFwcw/vDiNXEYrXIYDe5j/GMrkePYLuOgR4rBq+2DS
slTQvcM6eN7fR2FqfPrYJ45+oeIO2LOu86B9wYjF53jPz2FtEdnYHwxxCZNgn5n0
EJ8TFjP77mLV65vPA8e8ARIKP2bpRpbYsSSSwoKomo7P6wuf4Owxh8obd9IkeFVb
tZWJQ2E90H1QP8GiXOs1Fs+Q2YqjzWU456GkH7aSPfYijTjaHHTxPy4hQHciRfpZ
j0CjC77MXI3YC0Zi4BeRHOApaAtUgldMmHGTb0LJoqpeWiWsUR9LfXOBafYScRdZ
mFP+Ey6v6VL0teFNqc6wgThdIEWwHHb+hMx4Slr87IbOr+vbMMNptZ7/Z3tUxILx
1eRyhmzyh+MGJBx/lxY5oMD0vgrfQNx6tcCsGDHmBxUXIJrPqsodk+PXPT4PQnRT
CkNYiNUyJSmlGl/mFQGTYWKcOI/LPf/8bIqJF3DKlVuIuM8hWVhJSdcjEq/+e+AY
E3+BxV4FGvdtOQJeSvXgTqIJxyUXgx1Z5dMmAUT5E9c+NmFQlm0IH2wDcogg9jQD
mUj164vsl84Ce1taflj49uRL6HT/PPT9XXcniGuWHM6ArDsVM6ZQYo7HMsQkF3Dv
bVECAwEAAaMWMBQwEgYDVR0TAQH/BAgwBgEBAQIBAjANBgkqhkiG9w0BAQsFAAOC
AgEAmdBLyHY8DfccPSvRQrwSHUQTu9Z0/aaSIS6Ngk3zjyodY/4piNsZnW/XppT+
LDXbtwDM70WXflOEZkbSO2bSA2zfCbcp2KLn/ZwTY8eM7RQr/rH7+L+LRlUa54We
SqpPXHuZe1mIji8adQC0hF+I8x6ofNwhbpwXmbIeAGolCBTY/tm8mCwmDkeRLCRY
+9DtPkC03wpzlQJGUeCUd9eEAYs+YCF6kKmEnN0Rq1ceNf/nYInzPLjlU0fwNaU7
lHNzoAKUIW+oNMMp0Qi8zgAzMTOEAbAUOvwlvSypc7nBPKF+T2gY65U4wpbLV3PU
4S2Apt4PdybvpuLIGfOYlm2sEQyAQJw45nU0/dKPNRgbeGmsKN4DCfPhK6uGuv92
Zpu9ycf48lz4SmAInkxengCNVSj2QPuazbAR6mXHrDf+KlmTnR5UD9/I4WKYZG4g
bDUVTg03a1rUKre3jnaaytVGxtegukfK1bikH45lPaA/6tl+W4LubztFDRKHj12k
1C2tyawLYaLn8U5R1WiQBxEf/MiZjYm38+5EWPn5FulUp54sSqNnGOVsIey0NM4+
J3PZz7wxC3R+JwyRjhN+JSwiUhpwF0WaqC1FLPr6sA8w5GzrgwHkpl6nK4hdjxzT
f4TZKAElsdW9NUgGOpIDYPhochDov7dVZMSNp17pcNJWeXE=
-----END CERTIFICATE-----
 2 s:/CN=iotedged workload ca
   i:/CN=Test Edge Device CA
-----BEGIN CERTIFICATE-----
MIIE0TCCArmgAwIBAgIEHaeK8jANBgkqhkiG9w0BAQsFADAeMRwwGgYDVQQDDBNU
ZXN0IEVkZ2UgRGV2aWNlIENBMB4XDTE4MDgxNDE0MzEwNFoXDTE4MTExMjE0MzAz
OFowHzEdMBsGA1UEAwwUaW90ZWRnZWQgd29ya2xvYWQgY2EwggIiMA0GCSqGSIb3
DQEBAQUAA4ICDwAwggIKAoICAQDJBVJvwX7XAlj1S5/kWkGRCgCKKhA7+FCJmlUv
+NELdQCEERU73Szm3hf1BOSSZVj3zX3SKbrw7+nOAHTYwvENpMfszmlutodQbnS7
4U0sQdSVWdHY1jyjG1bB0rgzpcwJFrBsPJtYaA/SnLkmp94c75wAJ//HCa12Xzru
LGZ7RKChFuTrChplj0SjxWtDkGlDJoAAfk9DkPBVcYdIPLkLl6fvQ/MZtEb1RCM1
VlOMjutBsSWi9F42oMl1b1fU5xtij9fGhE3+OOIUlQZeg9lyUppls7sLL5U5yjFN
UjmOkm6RD5gS8BJKdDpVOm7Q+zkAs4zuU4K5o9akvn5JO3RHcI1/gRMnqq4x1hv5
AB48Gv/PkSwRVp/DYofJUy4nUpsOR29IzZ7tDFd4/Q8uOqignvhwL9zPgE1fO8LP
AM7r4V3n0sg1lgBIg/dimzyrIRDu4yc82QIPIGXxOMXK1Soqai/wBnrG9P7Y+vss
Eri87jO8ms13GZw1qvAmLMKP2zL3ymQpP2uP6pw06lqM3BYo6s4VaavEXevY4HiM
vUN476fE6qGkPacGN+aNpwafCwaIcuryFAmiZjOGiJ3j8fPU/Gquns/eVIdiQeb2
hiIXQPWV3GcPqqT+1y600pYVEz9nlwmYtSYgpsqDQstdBB28IqePKKXC+CIMo4+k
2GzsiwIDAQABoxYwFDASBgNVHRMBAf8ECDAGAQEBAgEAMA0GCSqGSIb3DQEBCwUA
A4ICAQBXcrPzLgQm/Jdj57AzvvT6PK//10CFGNdYi4/E7cIM3xok+YRgP0e+6VTh
M5jg+8wjHokW7MTs6FRTQS6d5jObFGBO29AANMWSZNeRsU/aXTGK5XKuXM3UcZGk
x4p0lQYsaNPEiVjtZL2PeZ3+KNldAO2cXhWGiXIBQiYe7VBRI9VSw/wkH3VP7WtG
NOaPFZ3vYmCqUUwSsgDQ8La3Bwj+0X1gTnyqG6yMsUhWWk0YsnN+0PsQ/n8/8nat
4eb/nh9X98jU88506Fd2yZaRj4NYG5RvS0kQqyDYSbODsipKwVtTpgeS2Ozm6QGv
a6Z8RPn77TNeLJHyO2SyvhQpetowsYdPLP2uSvFoT6kdqAnU3Ttr4ehTBCaccDjQ
3p4wOxInVqOzreO+zLlMIoTCNGZN1HfeF0MRiXb2jyBE+pJHOeaYZFdaigW+o5Hv
1V1eX5V1mThnGnsweqrIRdo1VXYWWHpDeRaCi9SBzqp0t1IV37NqCe0fpXPNgxmj
CGGREnMn+Fk6tmBK19ni5RBONTV6+RyOBs2CdClIjLflPWi1bttres4qDvFI2B8M
fKW6/3K6bA3ZXPtLMiTJdhikrtN/WBEtibBuPt/MxpD7zQBXnxYjPbF9FsVeF8R5
4/nHDHPTSrcD4zWM7aN4LRm59VYWJsMYN+/PKlEVtmoCNOBAFA==
-----END CERTIFICATE-----
---
Server certificate
subject=/CN=iotedgegateway
issuer=/CN=iotedged workload ca
---
No client certificate CA names sent
Peer signing digest: SHA512
Server Temp Key: ECDH, P-256, 256 bits
---
SSL handshake has read 4099 bytes and written 302 bytes
Verification error: unable to get local issuer certificate
---
New, TLSv1.2, Cipher is ECDHE-RSA-AES256-GCM-SHA384
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
    Protocol  : TLSv1.2
    Cipher    : ECDHE-RSA-AES256-GCM-SHA384
    Session-ID: 7947C8E2DF4B97416F4BEFFE633149BBB2755C01F93D136C828B732CBBB138A4
    Session-ID-ctx:
    Master-Key: 5BC2A4C12B44B423AFA1C7C8E088DA784029FBD34CE898EF67D55158A12F3D670902CD1B8D975522109459E244856AA2
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    TLS session ticket lifetime hint: 300 (seconds)
    TLS session ticket:
    0000 - b5 ac b9 47 89 49 05 8d-90 5c dc 3a c0 00 20 05   ...G.I...\.:.. .
    0010 - e5 64 a3 38 f8 d2 02 ae-fb 72 d8 e6 9b 2a 47 e2   .d.8.....r...*G.
    0020 - 70 c8 ed 32 73 34 bb 3d-0e 85 95 1f a3 a5 e9 b5   p..2s4.=........
    0030 - 04 aa 6f 74 a6 01 ad 64-5e 41 5d ee 97 55 83 f3   ..ot...d^A]..U..
    0040 - c7 8b 0f 82 81 fe f2 4e-1e 98 23 e9 1f 52 6e c2   .......N..#..Rn.
    0050 - 85 be 8f 43 85 da fd d3-87 22 4c 24 6d ad c0 b1   ...C....."L$m...
    0060 - 1f bf de d1 75 f7 ac 64-e4 67 f6 53 d2 b9 17 a8   ....u..d.g.S....
    0070 - 96 98 f2 25 bb 7d 2f d0-67 ec f5 c5 62 4a 89 0c   ...%.}/.g...bJ..
    0080 - b0 39 37 35 f8 ed 36 ac-6b ee 87 52 33 ed ed 9c   .975..6.k..R3...
    0090 - e2 a9 5d 7d e1 c5 d4 49-ca d9 1e 5d ec 45 3c 15   ..]}...I...].E<.

    Start Time: 1534259155
    Timeout   : 7200 (sec)
    Verify return code: 20 (unable to get local issuer certificate)
    Extended master secret: no
---
read:errno=0

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

ID: 71acc49c-a23e-493f-c3f5-4ec46846616c
Version Independent ID: bd3abb8d-1b48-0efd-f6a4-1b3f7a12c039
Content: Create a transparent gateway with Azure IoT Edge - Linux
Content Source: articles/iot-edge/how-to-create-transparent-gateway-linux.md
Service: iot-edge
GitHub Login: @kgremban
Microsoft Alias: kgremban

@MaWa19 Thanks for the feedback. We are actively investigating and will get back to you soon.

@MaWa19 can you please follow the instructions from here and let us know if you were successfull? Thank you.

@sergaz-msft Thanks for your quick reply. Unfortunately the linked instructions didn't solve the problem. In fact, I did the proof of ownership already while trying to solve this issue. Are there any debug files I could inspect to see where the error is coming from?

@MaWa19  you are welcome.

In fact, I did the proof of ownership already while trying to solve this issue.

What is the error that you see now? When you perform "openssl s_client -connect localhost:8883 -CAfile /home/pi/work/certs/azure-iot-test-only.root.ca.cert.pem -showcerts" you should see "Verify return code: 0 (ok)"
What is the ‘hostname’ in config.yaml ? It should be "localhost" in order for it to work.

@sergaz-msft the error was the same as before..
@stevebus I guess the error was in fact related to the hostname. Currently I don't have a real DNS server since this is just an exemplary implementation for now. Today I got a little bit further and was able to establish a connection between the leaf device and the gateway using the owner certificate in /var/lib/iotedge/hsm/certs. However, I was still not able to set up a connection using the azure-iot-test-only.root.ca.cert.pem.
How are the certs in  /var/lib/iotedge/hsm/certs related the the ones I created along the process? I won't be able to test your suggestions before Sunday but they sound promising so far.

This is an implementation detail that is always subject to change, but regarding how the certs are related....   the certificate that you create with the certGen create_edge_device_cert command actually created an intermediate certificate.   That intermediate certificate, which really you can think of as being a 'machine level' cert is used, by the iotedge runtime (specifically, the iotedge daemon) to generate another cert that we refer to as the "workload CA cert".   That cert is used internally by the edge runtime for several thing, one of which is to then generate the actual cert that is presented by edgeHub to connecting downstream leaf devices (let's call that the 'edgeHub server cert').  So that final cert is the cert that is presented to clients when they try to establish a TLS connection with edgeHub.  When the edge runtime generates that cert, it uses the 'hostname' entry in the config.yaml file as the Common Name (CN) of the edgeHub server cert.   So, the hostname in config.yaml must be the same name that your downstream leaf devices will use to connect to IoT Edge (for example, in the GatewayHostName parameter on the connection string if you are using our SDKs) and, as an aside, the name that you would use in your openssl command above.   So, you can't use localhost for that name as downstream devices would not be able to resolve localhost to the Edge device.
So, the certificate chain is
root ca cert* -> intermediate ca cert* -> device ca cert*  ->  workload cert^ -> edgeHub server cert

generated for dev/test using our developer scripts (certGen.sh)
^ - generated under the covers by the edge security daemon

does that make sense?
If this is a POC/sample/etc (i.e not production, in production you should use a real FQDN), you can just make up a name to use in your hostname entry in config.yaml.   For example, mygateway.local or something like that.   then, in the absence of real DNS you can add an entry in your hosts file (/etc/hosts on Linux, \windows\system32\drivers\etc\host on Windows) on both your edge box (so you can test with your openssl command) and then on your downstream leaf device.  Just make sure you can ping that name from the various boxes after you make the entry.

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: MaWa19 TravisCragg-MSFT sergaz-msft stevebus


text:
The "Debug a remote Service Fabric application" does not work as advertised

I tried this the other day.  Below is how it worked for me:

attaching to the application worked only on like every 5h attempt.
once the breakpoint was hit, it took the debugger forever to evaluate the local variables.  It never went through to completion.

The feature sounds to be amazingly good "on paper", a total waste of time to try to use it.

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

ID: e8adfa1c-0bb9-c112-3463-0d655a3e7cd1
Version Independent ID: ef09b17d-cebf-56ca-7f59-71dba2dc3123
Content: Debug your application in Visual Studio
Content Source: articles/service-fabric/service-fabric-debugging-your-application.md
Service: service-fabric
GitHub Login: @vturecek
Microsoft Alias: vturecek

@eugen-nw thanks for bringing this up. The performance might vary based on your computer specs as well. Can you tell me what specs you are running VS on?

@eugen-nw thanks for that! You are running a similar machine to mine so I will try to repro and see if I get similar behavior. Just FYI I am out of office tomorrow so I will run some tests first thing next week and provide an update. If you notice anything else you believe might be worth noting just let me know :)

Thanks again Micah!  I'll be on vacation next week, so I won't follow up on this before Sept. 10.
There's another inconvenience I just recalled: Visual Studio was not able to load the .PDB symbols that were placed next to the running binaries in Service Fabric, so I needed to download them onto my laptop and load them from there.  This is merely an inconvenience that needs to be 1). documented 2). hopefully, be  addressed.

Thanks for letting me know :) I will be sure to provide updates but not expect a response till you are back so no worries. Enjoy the vacation!
And thanks for that extra information. I will make sure to note that as well and we can see if we can note that in the doc or find a way to make the debugger better so that doesn't happen.

@eugen-nw I ran through this doc and although I did not see the exact same issues as you did the entire process itself was not super fluent. I am assuming this is because the doc was published in 2017 and since then their have been mulitple updates in the SDKs.
I was able to get the debugger to work but not very smoothly.
@vturecek would you be able to run through this doc and see if we can add some updates where needed? If anything we should make sure it is updated to work with the latest SDK versions.

Even I am facing the same issue as eugen-nw trying to debug a SF Application deployed in Azure.
VS 2017 doesn't download the application code symbols at all even from the local location. Do we have any fix for this in place?

It’d be interesting to learn if the feature works for anyone

@MicahMcKittrick-MSFT Do you guys have a fix in place for this? I enabled remote debugging using VS and it completed all tasks. However, after that, I could not attach to debugger - as other people have mentioned, it says: "Failure to launch Remote Debugger" - this is very frustrating, as it always happens wth MS product that it does not work as advertised when it is most needed.

authors: MicahMcKittrick-MSFT Nisha2015 eugen-nw tejasavora


text:
Error

Index.js, not Index.html
Call API results in "Unauthorized"; how is the desktop app supposed to work without changing references to "fabricam..." in App.xaml.cs ?

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

ID: df26c5f6-63b9-d281-5724-c0731546b087
Version Independent ID: 239bf87c-fcf0-b35e-744d-fecbb55501e4
Content: Tutorial - Grant access to an ASP.NET web API from a web app using Azure Active Directory B2C
Content Source: articles/active-directory-b2c/active-directory-b2c-tutorials-web-api.md
Service: active-directory
GitHub Login: @davidmu1
Microsoft Alias: davidmu

@mcurko Thanks for the reply! We will investigate and update as appropriate.

Hi @mcurko , are you referring to a particular Github sample?

I'm referring to this description: https://docs.microsoft.com/en-us/azure/active-directory-b2c/active-directory-b2c-tutorials-spa

authors: MarileeTurscak-MSFT mcurko


text:
Client credentials token is not working for onprem exchange server.

In hybrid setup if client credentials grant type is used to get token and if that token is used to get on-prem user messages  (https://graph.microsoft.com/v1.0/users('onpremuser@onpremdomain.com')/messages/) using graph api it fails by providing UnknownError.
When debugged on IIS logs  error shown was "This token profile 'V1S2SAppOnly' is not applicable for the current protocol.";error_category="invalid_token".
However if authorization code grant or resource owner password credential (ROPC) grant if used to obtain token , we were able to get messages of on prem user using graph API.
Have attached screenshot of token for both. How to make client credentials grant work for on-prem user messages access using graph API (in hybrid setup) ?

@karthikhebbar Thank you for your feedback . We will investigate and update this thread .

Ignore aud in first token. Even if aud is https://graph.microsoft.com (resource) same error is seen. I was inter using resource and scope to test and mis pasted token of scope which is refering to Azure AD API instead of microsoft graph api.

@karthikhebbar I suggest you please open a new MSDN forum post with the details and community will help address your query. Please refer to below link to MSDN forum to ask new question -
https://social.msdn.microsoft.com/Forums/azure/en-US/newthread?category=windowsazureplatform&forum=WindowsAzureAD&prof=required.  Please provide the MSDN link over here so that I can help you getting answered.

I have asked question in forum. Below is the link https://social.msdn.microsoft.com/Forums/azure/en-US/f6300a96-b762-404b-b585-34a420c633e7/client-credentials-token-is-not-working-for-onprem-exchange-server?forum=WindowsAzureAD
Please help me in getting this issue solved. Thanks

@karthikhebbar Sure. We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


text:
Windows Server 2019 Supported?

Assumed when Windows Server 2016 is referenced it should also include Window Server 2019 for Review Supported Devices?

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

ID: 72cdc251-618a-e84e-f40d-960b0ac69f99
Version Independent ID: 8cbaba3c-e883-2c71-28fb-f88db3fcaf7d
Content: How to plan hybrid Azure Active Directory join implementation in Azure Active Directory (Azure AD)
Content Source: articles/active-directory/devices/hybrid-azuread-join-plan.md
Service: active-directory
Sub-service: devices
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@D-Jeffrey
Thanks for your feedback! We will investigate and update as appropriate.

@MicrosoftGuyJFlo
John, could we include Windows Server 2019 in the Supported Devices list ?

Adding update to PR in private repo

authors: D-Jeffrey MicrosoftGuyJFlo neeleshray


text:
Does Backup for Azure File Shares support incremental backup?

Hello,
Does the Backup for Azure File Shares will be done as full backup only?
Or does it support incremental backup?
Thanks

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

ID: 61c0f8e6-5a57-58aa-ecd6-2bf83809c44d
Version Independent ID: ee8b8f60-bffd-e6ec-5f21-bfd3208fc511
Content: Back up Azure File Shares
Content Source: articles/backup/backup-azure-files.md
Service: backup
GitHub Login: @rayne-wiselman
Microsoft Alias: raynew

As per this article, incremental backup is supported by all Azure Backups. so yes, Azure file shares support incremental backup.

We will now close this issue for now. If there are further questions regarding this matter, please reply and we will gladly continue the discussion.


text:
How to send data for multiple "time" points

Would you post an example JSON file that feeds data for multiple "time" points?
I tried below but got invalid JSON format error.
[
{
"time": "2018-09-16T10:00:00",
"data": {
"baseData": {
"metric": "QueueDepth",
"namespace": "QueueProcessing",
"dimNames": [
"QueueName",
"MessageType"
],
"series": [
{
"dimValues": [
"ImagesToProcess",
"JPEG"
],
"min": 3,
"max": 20,
"sum": 28,
"count": 3
}
]
}
}
},
{
"time": "2018-09-16T10:05:00",
"data": {
"baseData": {
"metric": "QueueDepth",
"namespace": "QueueProcessing",
"dimNames": [
"QueueName",
"MessageType"
],
"series": [
{
"dimValues": [
"ImagesToProcess",
"JPEG"
],
"min": 3,
"max": 20,
"sum": 28,
"count": 3
}
]
}
}
}
]

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

ID: 78411727-ea56-aef5-4f04-b016c25afba9
Version Independent ID: 8687b7bc-a196-6fd0-fa57-9fa5dd2d4545
Content: Send custom metrics for an Azure resource to the Azure Monitor metric store by using a REST API
Content Source: articles/azure-monitor/platform/metrics-store-custom-rest-api.md
Service: azure-monitor
Sub-service: metrics
GitHub Login: @anirudhcavale
Microsoft Alias: ancav

Thanks for your comment. We are actively investigating and will get back to you shortly. Thanks for your patience.

@anirudhcavale - is it possible to update the document with a sample JSON for the requested scenario?

@anirudhcavale - any update on this please?

#label:"CreateAzMonWIFeb2021"

Thank you for your contribution to the Azure Monitor documentation. We have created a workitem for this issue in our internal backlog database. We will prioritize it and make any necessary changes as we are able.
#please-close

authors: femsulu kulmam92 pritamso rboucher


text:
Conditional Access and Configurable token lifetimes

Hi
I understand from the documentation provided that Configurable Token Lifetime policy will not be used to configure refresh tokens from the 1st November.
https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-configurable-token-lifetimes
Can we get a bit more clarification on what Microsoft's plans are, as from following these discussion threads it seems like there has been some confusion in the community on this issue.
I understand that Access tokens set via Azure Configurable token lifetimes will not be deprecated after 1st November so my understanding is that Configurable Token Lifetime policy will enhance (not supersede) the existing features provided by Azure by providing support for rolling windows, persistent browser sessions and more governance over application access.
Are there plans in future to let Conditional Access define access tokens or is the Configurable Token lifetime policy here to stay?

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/develop/active-directory-configurable-token-lifetimes.md
Service: active-directory
Sub-service: develop
GitHub Login: @rwike77
Microsoft Alias: ryanwi

@LachlanJB Thank you for your feedback . We will research on this and update this thread.
Thank you.

Hello @LachlanJB regarding :

Can we get a bit more clarification on what Microsoft's plans are, as from following these discussion threads it seems like there has been some confusion in the community on this issue.
I understand that Access tokens set via Azure Configurable token lifetimes will not be deprecated after 1st November so my understanding is that Configurable Token Lifetime policy will enhance (not supersede) the existing features provided by Azure by providing support for rolling windows, persistent browser sessions and more governance over application access.
Are there plans in future to let Conditional Access define access tokens or is the Configurable Token lifetime policy here to stay?

All updates in regards to this can be found on the tech community blog found here : https://techcommunity.microsoft.com/t5/Azure/ct-p/Azure
and here: https://azure.microsoft.com/en-us/updates/
Currently there are no updates in regards to this, so although refresh tokens have moved to the new authentication session management, access tokens currently are remaining to use policies.
If you're interested in this feature please submit it at the uservoice here and if there's enough community support for this, the product team will look into implementing it accordingly : https://feedback.azure.com/forums/169401-azure-active-directory

@LachlanJB Please let us know if there are anymore questions within the scope of this git issue. If not, I will be closing out this git issue by end of day today. Please reopen this git issue if you have anymore concerns. Thanks

@LachlanJB Hope the above clarification helped you . Should you need any further help , please let us know. We will be closing this issue now.

Hi
Just a couple questions and observations to point out since I last posted.

I noticed that the cutoff date mentioned at the top of this article has been moved to May 1, 2020.

Yet this document still says 1 November 2019 "Microsoft plans to retire the configurable token lifetime feature on November 1 and replace it with the Conditional Access authentication session management feature."
https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/howto-conditional-access-session-lifetime
(I assume that this is an oversight and needs to be corrected)

Secondly I would like to clarify the proposed changes that Microsoft will make to the Policy Definition Properties
Policy Definition Properties

Currently a policy definition has the following properties.
Access Tokens
AccessTokenLifetime
Refresh tokens
MaxInactiveTime
MaxAgeSingleFactor
MaxAgeMultiFactor
Session tokens
MaxAgeSessionSingleFactor
MaxAgeSessionMultiFactor
As I understand not all of these properties need to be defined in a policy as they each have a default value if none is assigned. However once the session and refresh tokens are deprecated can we expect to see any changes in the policy definition property and how that is programmed via PowerShell? I.e will the cmdlets for the definition property be automatically updated to remove the deprecated properties for refresh and session tokens or will they remain but just have no effect?
Lastly, I am investigating how this change will effect SharePoint On-Premise 2013. Our testing so far has shown that SharePoint 2013 on-premise doesn't support refresh or session tokens so in this situation we only have to be concerned with access tokens thus this update should not be relevant to us - but I am interested to understand how this update will effect existing policy definitions just so we are aware of any changes.
Thanks!

authors: FrankHu-MSFT LachlanJB shashishailaj


text:
Ghost record cleanup process?

Does this feature improve ghost records management related to long running transactions and Always On?

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

ID: a825ecf0-9d63-29be-8e8a-aab285a53c7a
Version Independent ID: 4e25d0f7-56b5-3229-89d8-7509264647a5
Content: Accelerated database recovery - Azure SQL Database
Content Source: articles/sql-database/sql-database-accelerated-database-recovery.md
Service: sql-database
Sub-service: high-availability
GitHub Login: @MashaMSFT
Microsoft Alias: mathoma

@brettshearer Thanks for the Comment. We are actively investigating and will get back to you soon.

@brettshearer Ghost records were an issue when running SQL server on a VM.
I am curious to understand how ghost records are a cause of concern in Azure SQL since
backup and clean up processes are handled by the system automatically.

I am referring to on premise SQL server. Ghost records occur when the longest running transaction has started before a row is deleted. The row transaction commits, but waits for the long running transaction start LSN to move past the row delete LSN.  In the case of Always On where there may be a report or other extraction occurring for many minutes, deleted rows build up quickly in tables such as those used for queues or sequential number generators.
The only workaround to date is to perform a rebuild of the table. Whilst this does work in principle, getting the SCH-M lock can prove difficult.

@MashaMSFT Could you please help here.

@MashaMSFT Please check the user question and help regarding this issue further.

Hi @brettshearer , thank you for contacting Microsoft! There is no interaction between ADR and ghost cleanup, so ADR doesn’t help with ghost record cleanup.
Versioning generally affects ghost record cleanup since we need the ghosts to be preserved while there are long running transactions that might need to access them, but this doesn’t change with ADR.
I hope that helps and please let us know if you have any further questions? If not, we will proceed with closing out this Git Issue in a few business days.
Thanks!
Masha from the SQL Docs team

Hi @brettshearer , it's been some time since we've heard from you, so we're going to assume that your question has been addressed and close out this Git Issue. However, please feel free to respond via comment should you need anything further.
Thanks again for contacting Microsoft and hope you have a wonderful rest of your day!
Masha from the SQL Docs team

authors: KalyanChanumolu-MSFT MashaMSFT NavtejSaini-MSFT SadiqhAhmed-MSFT brettshearer


text:
Redirect http to https clarification

At bullet 10 (creating the redirect http to https rule), can there be some clarification on the following points:

Why is 302 used? I would expect it to be permanent (it isn't like we want to revert to http again in the future, and less traffic/redirects from FrontDoor is desirable).
Why is 302 chosen (allows changing POST to GET) over 307/308, where changing POST to GET is not allowed?

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

ID: 908053a8-ebc0-35ec-87ad-24e59f587eb9
Version Independent ID: c8b90a6a-c37f-68eb-1e1d-54322eae9324
Content: Create a Front Door with HTTP to HTTPS redirection using the Azure portal
Content Source: articles/frontdoor/front-door-how-to-redirect-https.md
Service: frontdoor
GitHub Login: @sharad4u
Microsoft Alias: sharadag

#reassign: jessie-jyy

The redirect type can be set to 301/302/307/308 per customer needs.
301 is the recommended status code for HTTP to HTTPS redirection. See URL redirect
The instructions in Create a Front Door with HTTP to HTTPS redirection is recommending 302 which is inconsistent with the first link. We will fix this. Thanks for pointing this out @jeroenwo

The article has been updated and should reflect later today. Will archiving this issue for now. Please feel free to contact us if you have any questions. #please-close

authors: Harikrishnan-M-B duongau jeroenwo


text:
App Service Linux: VNET integration causes application and docker to not respond at all

Hi all,
I know the VNET integration is still in Preview, however i hope someone can still help me out with our current issue. I have on my developer tenant an app service linux with VNET integrated to access a Storage account (v2) behind VNET.  The web service application is python based and makes use of gunicorn/flask for http requests and azure.storage.blob  package for interfacing with the storage account.
This all works well on that tenant however we now try to get the same solution working on a different tenant and this causes problems. We use the VNET integration feature which is in preview, endpoints are also configured (Microsoft.Storage and Microsoft.Web), however when we start the App service after integration we do not get any response, also no docker logging is available, logging stream doesn't react. In the developer tenant we got an immediate response back.
Also it doesnt matter how long you wait for the VNET integration (as can be seen as notification). When you try to disconnect the VNET integration also an error occurs :
"VNet could not be removed from web app:
The gateway did not receive a response from 'Microsoft.Web' within the specified time period."
Interestingly enough after that the VNET integration is not visible anymore, and when we start the app service again everything works again. We also tried using an empty virtual network with only the app service integration enabled which gives the same problems. Both the software and configurations are exactly similar, also we use West-Europe for all the resources.
Does anyone have any idea where we could look further to pinpoint this issue? Or is it because it is still in preview and depending on location it could or could not work....
Regards, Jos Eilers

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

ID: a7a98803-1438-b1b5-f543-7dd88bc4294e
Version Independent ID: 37ff1d0f-ed8e-5e4d-1f4c-1b9f6cffb938
Content: Integrate app with Azure Virtual Network - Azure App Service
Content Source: articles/app-service/web-sites-integrate-with-vnet.md
Service: app-service
GitHub Login: @ccompy
Microsoft Alias: ccompy

@jos1977 Thank you for the question! In order to best address your question, could you provide us with the URL of the MS Doc that you were following, if any?

@BhargaviAnnadevara-MSFT : Sure!, this would be at least the following : https://docs.microsoft.com/en-us/azure/app-service/web-sites-integrate-with-vnet

@jos1977 Thank you for the response! I've routed this to the appropriate Team to investigate and update.

@jos1977
Announcing general availability of VNet Integration with Windows Web Apps
One of the issues that App Service customers need to solve is how to access resources in their Azure Virtual Networks (VNets). To solve that issue, a feature was launched in 2014. The older VNet Integration feature required a virtual network gateway and really only supported reaching into the VNet. There was still a major need to be able to use networking features like Network Security Groups (NSGs), Route Tables (UDRs) and Service Endpoints. A new VNet Integration technology was developed to solve these problems while also being easier to use.
The new capability is referred to as regional VNet Integration because it will only work with VNets in the same region as the app. This new capability has been in preview for a little while already but only supported making calls to RFC1918 (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) addresses and service endpoints. The regional VNet Integration feature now supports sending all outbound calls into your VNet. You can now use features like Network NSGs and UDRs against all of the outbound traffic from your web app.
By default, if you use regional VNet Integration, your app will still only route RFC1918 (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) traffic into your VNet. If you set the app setting WEBSITE_VNET_ROUTE_ALL to 1, your app will then enable all of the outbound traffic from your app to be subject to NSGs and UDRs.
These new changes enable you to:
•	access non-RFC1918 endpoints through your VNet
•	secure all outbound traffic leaving your web app
•	force tunnel all outbound traffic to a network appliance of your own choosing
The pre-existing gateway required VNet Integration feature will continue to be supported. It supports integrations with VNets in other regions, or Classic VNets. This feature is available in all public regions. Regional VNet Integration for Linux apps is still in preview. Today's general availability announcement is only for windows apps. To use regional VNet Integration, your app must be in a Standard, Premium, Premiumv2 or Elastic Premium App Service plan. The feature is not support in an App Service Environment which is already in a customer VNet. Regional VNet Integration is only for outbound calls being made by your apps. It does not enable private access to your apps.
For more information about regional VNet Integration, read App Service VNet Integration For more information about App Service networking features in general, read App Service networking features

@jos1977 , Please let me know if you have further queries.

@DashleenBhandari-MSFT :
I checked the general text above for any requirements concerning App Service Linux and VNET integration and see the following :

It only supports calls to RFC1918  and service endpoints. At the moment we use the 10.0.0.0 range for both the blob storage accound and the the app service so this should be okay.
The app service must be in a S , V or V2 service plan. The app service we use is in a V2 service plan (also the test i performed in my own developer tenant was in a V2 service plan)
VNET integration is only for outbound calls: The app service makes calls to the storage account for uploading/downloading blobs only, so i think this is also okay.

So far i dont see anything mentioned here that could cause the problems we have now, apart from the fact that it is Preview functionality we are working with.

@jos1977 , I will go ahead and close this issue. Feel free to reopen if you have further queries.


text:
process.env error

Error happened for process.env
'process' is not defined

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

ID: a98279c3-7183-f0ee-4378-e8a232b6ba22
Version Independent ID: c59ccc3e-b157-bb6a-5926-fd52a17f65a2
Content: Quickstart: Generate a thumbnail - REST, JavaScript - Azure Cognitive Services
Content Source: articles/cognitive-services/Computer-vision/QuickStarts/javascript-thumb.md
Service: cognitive-services
Sub-service: computer-vision
GitHub Login: @PatrickFarley
Microsoft Alias: pafarley

@hEi872 we will review your feedback and get back to you shortly. Thanks.

@PatrickFarley please can you help with this issue? Thanks.

Hi @hEi872 , I couldn't find an immediate fix so I'm asking others on my team to take a look.

@hEi872 , I've updated the JavaScript quickstarts, please have a look again.
The issue was that HTML-based JS cannot use the process construct - it's only for NodeJS.
#please-close

authors: GiftA-MSFT PatrickFarley hEi872


text:
URL Syntax for Sharepoint

I'm trying to create OData Linked service for SharePoint to copy data from SP to storage account. Can you specify what should be the URL format for that? Do you have any working examples of such actions?

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

ID: 8193f2a3-80f3-14e9-7022-27ea5fa02001
Version Independent ID: 9eff4721-c265-74a7-11fd-c6920f309982
Content: Copy data from OData sources by using Azure Data Factory - Azure Data Factory
Content Source: articles/data-factory/connector-odata.md
Service: data-factory
GitHub Login: @linda33wj
Microsoft Alias: jingwang

@jkrysicki
Thank you for reaching out and bringing this to our notice. At this time we are reviewing the feedback and will provide an update as appropriate

@jkrysicki : Not sure if you have already gone through this thread . https://social.msdn.microsoft.com/Forums/en-US/72a648d8-63af-4886-bf17-fa2323622ac6/non-availability-of-microsoft-components-as-a-linked-service-in-adf?forum=AzureDataFactory
We will go ahead and assign this to the content owner , they will evaluate and make the necessary updates .

Related note - we are actually working on enabling a new Sharepoint Online List connector to make it easier to copy data from SPO list. Stay tuned.
With current generic OData connector, Sharepoint Online Site URL would be something like https://[Tenant-Name].sharepoint.com/_vti_bin/listdata.svc/ if it does not contain any sub site, or https://[Tenant-Name].sharepoint.com/sites/[Site-Name]/_vti_bin/listdata.svc/ if it contains multi sub sites.
#please-close

authors: KranthiPakala-MSFT himanshusinha-msft jkrysicki linda33wj


text:
Azure App Service Linux Container <==> Web Socket from Twilio  not working

Hello
All of these solutions did not work for me:
Let me explain what I have:
I'm developing a solution with Twilio + Azure Cognitive Services (telephone based conversation, realtime, and using websockets)
From Twilio, when a call comes in, I send an initial POST request (Webhook) to my WebApp for Containers like this:
https://my_azure_web_app.azurewebsites.net/twiml
Inside <my_azure_web_app> server I have an end-point like this:
class TwiML(tornado.web.RequestHandler):
def post(self):
response_str = './greetings.mp3'
response_str += ''
response_str += ''
self.finish(str(response_str))
def set_default_headers(self):
print("setting headers!!!")
self.set_header("Access-Control-Allow-Origin", "*")
self.set_header("Access-Control-Allow-Headers", "x-requested-with")
self.set_header("Sec-WebSocket-Extensions", "permessage-deflate")
I can launch my app on localhost and into a container on localhost (i.e. I can open websockets from/to Twilio with no problem and get the websocket channel opened)
When I deploy the image into WebApp for Containers, and this container is running, I can receive the first part of the audio message (i.e. greetings). But, after that, I can not open the wss websocket connection (wss://my_azure_web_app.azurewebsites.net.azurewebsites.net/socket) and I always receive an error from Twilio like this:
Stream - WebSocket - Connection Broken Pipe
(I used the "EXPOSE 8080" into my Dockerfile and "WEBSITES_PORT = 8080" into my Configuration Settings WebApp)
The container is running:
2020-04-08 14:13:06.366 INFO - Logging is not enabled for this container.
Please use https://aka.ms/linux-diagnostics to enable logging to see container logs here.
2020-04-08 14:13:06.882 INFO - Initiating warmup request to container my_azure_web_app_8_91af842a for site my_azure_web_app
2020-04-08 14:13:10.919 INFO - Container my_azure_web_app_8_91af842a for site my_azure_web_app initialized successfully and is ready to serve requests.
I can access to its url:
https://my_azure_web_app.azurewebsites.net/
I can connect to my websocket channel with Advanced Rest Client (Google)
"Connected to wss://my_azure_web_app.azurewebsites.net/socket"
I think everything is fine BUT when I try to open the "wss://my_azure_web_app.azurewebsites.net/socket" from Twilio, it is not possible
I tried everything with no success (both, tornado server and Azure ). So:
Web App for Containers
1.1. CORS: empty (and also: Allowed Origins ""). Both, without success.
1.2. WebSockets enabled ("On")
1.3. Scale Up Service Plan (P1V2)
Tornado server:
2.1. Set headers "Access-Control-Allow-Origin", ""
2.2. Set header "Sec-WebSocket-Extensions", "permessage-deflate" (is it necessary yet?)
I run out my ideas.
Anyone can tell new ways to try?
Thanks a lot in advance!

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

ID: b421fa01-1f39-28a5-78c2-63dd5700c8c5
Version Independent ID: 10ed9c91-16e0-d371-fcfc-d6d5a7f984b2
Content: Run built-in containers FAQ - Azure App Service
Content Source: articles/app-service/containers/app-service-linux-faq.md
Service: app-service
GitHub Login: @msangapu-msft
Microsoft Alias: msangapu

@lopejum Thanks for the feedback. We are investigating the issue and will update you shortly.

@lopejum, Apologies for the issue you encountered. Thanks for sharing a detailed description of the issue.  If I understand the issue correctly, it appears that you’re facing this issue only when trying it from Twilio but works via Rest client.
I wish to engage with you offline for a closer look and provide a specialized assistance, please send an email with subject line “Attn:Ajay” to AzCommunity[at]Microsoft[dot]com referencing this thread and the Azure subscription ID, I will follow-up with you. As we will work with you offline, I will now proceed to close this thread.
Thanks for leverage docs feedback channel to raise this question.

authors: AjayKumar-MSFT RohitMungi-MSFT lopejum


text:
Github entity ID

In the page (Configure Azure AD SS - Step 4) there are directions to add a URL with an 'entity ID' but there are no steps where to pull that information from. I have looked at the GitHub directions and still don't see this. Since Microsoft also owns GitHub where do I get the 'entity id' from?

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

ID: 156e3923-74d6-432f-c5a0-b905520d4e7d
Version Independent ID: aeca7d10-15e2-9e42-74bc-5309a5108c05
Content: Tutorial: Azure Active Directory integration with GitHub
Content Source: articles/active-directory/saas-apps/github-tutorial.md
Service: active-directory
Sub-service: saas-app-tutorial
GitHub Login: @jeevansd
Microsoft Alias: jeedes

@over2under42 Thanks for the comment. We are actively investigating and will get back to you soon.

Hi, just enter in: https://, for example: https://github.contoso.com/

Hi @over2under42 , your entity ID for the SAML setup context is your GitHub organization name slug as seen in your organization's URL (e.g. MyOrganization from github.com/MyOrganization.) Hope that this helps!

Yes that help. The URL for step 4b. returns a 404 error page. Am I missing something?

@chetansriv and @v-pugoe can you please retest this app and update the doc @v-nagta ?

@over2under42 We have updated the article, please review
#please-close

authors: SadiqhAhmed-MSFT bruun963 jeevansd over2under42 rhoticity v-nagta


text:
UWP sample is out of date and references RecognizeSpeechAsync()

The UWP portion of how to use the Speech SDK tells the reader to insert code in the RecognizeSpeechAsync() method, which isn't present in any of the provided UWP source code. It appears to exist in the C# sample code only.

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

ID: e4b55e56-55a1-d635-6bea-271dc361d676
Version Independent ID: 8e9cb28f-c133-f310-3c7d-3a3b7e85f69d
Content: Quickstart: Recognize speech from a microphone - Speech service - Azure Cognitive Services
Content Source: articles/cognitive-services/Speech-Service/quickstarts/speech-to-text-from-microphone.md
Service: cognitive-services
Sub-service: speech-service
GitHub Login: @trevorbye
Microsoft Alias: dapine

@dreijer Thanks for the feedback. We are investigating the issue and will update you shortly.

@trevorbye Could you please review the following section Create a Speech configuration for Insert this code in the RecognizeSpeechAsync() method.
Here is the sample for UWP https://github.com/Azure-Samples/cognitive-services-speech-sdk/tree/master/samples/csharp/uwp/speechtotext-uwp/speechtotext-uwp
Could you please share any other samples available using the RecognizeSpeechAsync() method.

It looks like RecognizeOnceAsync() is the method that needs to be referenced in the documentation. @trevorbye is looking into this.

fixed the issue #please-close

authors: dreijer erhopf ram-msft trevorbye


text:
Determine length of Azure Table Storage entity

I tried the calculation for getting the size of the Azure Table Storage entity mentioned here: https://github.com/MicrosoftDocs/azure-docs/issues/35190#issuecomment-512117059
However, I have found that the limit is actually 88 bytes lower than what is documented, unless of course my code is wrong. Here's some example code: https://gist.github.com/joelverhagen/2bf45db3f5160bbfaf1056319b2172d0
Could it be related to storing the "ETag" property? I'm not sure if the etag always matches the Timestamp, that is stored this way:

4 bytes overhead for each entity, which includes the Timestamp, along with some system metadata.

I tried some different things such as adding additional properties (this doesn't seem to affect the 88 byte error) and simulating a fake etag property. The most logical thing I could find was that an "ETag" property stored as a string like this would take 88 bytes:
'2021-01-10T06%3A11%3A51.4183681Z'

| 8 bytes + Len(Property Name) * 2 bytes + # of Characters * 2 bytes + 4 bytes for the length of string
> 8 + Len("ETag") * 2 + Len("'2021-01-10T06%3A11%3A51.4183681Z'") * 2 + 4
> 8 + 4 * 2 + 34 * 2 + 4
= 88

But that's a wild guess. I'd be surprised if  the etag was stored just like that, with quotes and URL encoding :)
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 83df0ac8-6349-4ea5-4698-fdf00c69c92f
Version Independent ID: 5afd32d5-5585-c495-b68d-7d68963b6b3d
Content: Introduction to Table storage - Object storage in Azure
Content Source: articles/storage/tables/table-storage-overview.md
Service: storage
Sub-service: tables
GitHub Login: @tamram
Microsoft Alias: tamram

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

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

@joelverhagen Aplogies for delay in responding here! Have you referred to this article:  How the size of an entity is caclulated in Windows Azure table storage?

@joelverhagen Aplogies for delay in responding here! Have you referred to this article:  How the size of an entity is caclulated in Windows Azure table storage?

Yes, that was my original reference when implementing the calculation. However there are still 88 bytes unaccounted for as shown in my repro code.

Yes, that was my original reference when implementing the calculation. However there are still 88 bytes unaccounted for as shown in my repro code.

Hey @SumanthMarigowda, I don't know the answer to my question yet. Was the documentation updated? Based on my own experiments there still are bytes unaccounted for.


text:
Greater clarity regarding authentication cross tenant

[Enter feedback here]
The steps to authenticate need to be made clearer:
The SPN is created in tenant 1 which houses the gallery. The admin that creates the SPN in tenant 1 needs to authenticate against tenant 2 in the step outlined (it's not clear who has to do this step), but in order to succeed, the tenant 1 account needs to be added as a guest account in tenant 2 (no roles are required, just an account).
Error received:
User account 'app_admin@tenant1.onmicrosoft.com' from identity provider 'https://sts.windows.net/' does not exist in tenant 'tenant2' and cannot access the application in that tenant. The (tenant1) account needs to be added as an external user in the tenant (tenant2) first.

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

ID: b4c09d03-24b1-f376-34fd-cbfd8d29d3d7
Version Independent ID: 763073bf-734e-e079-2d4c-97c097eb7c88
Content: Share gallery images across tenants in Azure - Azure Virtual Machines
Content Source: articles/virtual-machines/windows/share-images-across-tenants.md
Service: virtual-machines
Sub-service: shared-image-gallery
GitHub Login: @axayjo
Microsoft Alias: akjosh

@bourgeoisrebel
Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate.

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

authors: VikasPullagura-MSFT bourgeoisrebel


text:
All non-guest users (see documentation) Link is not clear

The row Create Azure AD B2C directories | All non-guest users (see documentation)
has link to the top of the page https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/users-default-permissions
Is the purpose of the link to explain who are member users? If yes, link to section https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/users-default-permissions#member-and-guest-users will be better.
Also if there are only members and guests, will “All member users” be simpler than “ All non-guest users”?
I’ve tried to find on https://docs.microsoft.com/en-us/azure/active-directory/fundamentals/users-default-permissions page any B2C related info, but didn’t find.

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

ID: 0f9558c0-abb6-24f8-81c8-9000b80539e8
Version Independent ID: a4739135-863b-27bb-1f2e-cf297f21b4cc
Content: Delegate roles by admin task - Azure Active Directory
Content Source: articles/active-directory/roles/delegate-by-task.md
Service: active-directory
Sub-service: roles
GitHub Login: @rolyon
Microsoft Alias: rolyon

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

Thank you, @MNF. I agree that this makes and made a pull request to update the article. https://github.com/MicrosoftDocs/azure-docs-pr/pull/154712
@rolyon please review.

authors: MNF MarileeTurscak-MSFT


text:
could the static HttpClient be re-used by multiple users at the same time?

Suppose I defined a static HttpClient as below(per this doc):
private static HttpClient httpClient = new HttpClient();
Then there are 100 users calling this function at the same time, I want to know if the static HttpClient can be re-used among these 100 users? or each user have a HttpClient instance?

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

ID: cb8d85a7-1ca3-71f4-85fb-7fb02850b60e
Version Independent ID: 3d7daee4-fd6d-0e96-299a-90b3637e6150
Content: Manage connections in Azure Functions
Content Source: articles/azure-functions/manage-connections.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

Thanks for bringing this to our attention. We are actively investigating and will get back to you soon.

Hi @star286 - That's right, all 100 users will share the same connection pool owned by the same instance of HttpClient.
Per the doc for HttpClient:

HttpClient is intended to be instantiated once and re-used throughout the life of an application

@mike-urnun-msft , thanks for your information:). One more question, is this also true for documentdbclient / sql client?

@star286  That's right, DocumentDB client uses singleton which achieves the same thing and the SqlClient also does the same thing through ADO.NET.
Since we didn't determine any changes to this doc upon reviewing your feedback, we will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

authors: femsulu mike-urnun-msft star286


text:
It should show what all API Swagger UI exposes.

[Enter feedback here]
there should be some  screenshot  image which should shows  exposed API  in Swagger UI.

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

ID: ac742a64-1e66-4c89-6de5-67c7e818f9cc
Version Independent ID: 29714c95-3e4c-f153-0a6f-598a736b4564
Content: Install and run Docker containers for the Speech service APIs - Azure Cognitive Services
Content Source: articles/cognitive-services/Speech-Service/speech-container-howto.md
Service: cognitive-services
Sub-service: speech-service
GitHub Login: @aahill
Microsoft Alias: aahi

@samkuls we'll review your feedback and get back to you shortly. Thanks.

@aahill please review above feedback for doc enhancement. Thanks.

authors: GiftA-MSFT samkuls


text:
Regarding client machine insider group configuration.

[Enter feedback here]
Step number 2 of the "Requirements" section redirects to AVD Host Pool creation page.
Is the step about setting MSRDC client insider setting ? OR AVD Host Pool insider (which is confusing as there is no "insider" setting as such on AVD, not sure if its about "Validation" mode)
Further down there is a Step (number 4) which talks about a registry key for setting insider mode for the client.

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

ID: 715ab709-ac8a-1110-2042-969584102f3f
Version Independent ID: b8619d2b-1873-daa7-4932-13f0c89e7083
Content: Multimedia redirection on Azure Virtual Desktop - Azure
Content Source: articles/virtual-desktop/multimedia-redirection.md
Service: virtual-desktop
GitHub Login: @Heidilohr
Microsoft Alias: helohr

@ravibak Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

Thanks for the feedback. This article has been reworked including these specific points having been addressed. The changes should be visible later today or tomorrow.
#please-close


text:
Incorrect prerequisites in Container Apps Deployment Tutorial

The tutorial at https://docs.microsoft.com/en-us/azure/container-apps/deploy-visual-studio is incorrect in stating that as a prerequisite "Visual Studio 2022 Preview 3 or higher" is required.  The publish targets for Container apps aren't available until the 05/10/2022 release of Visual Studio 2022 17.2
Also see https://stackoverflow.com/questions/72331680/deploy-to-azure-container-apps-is-missing-from-publish-targets-in-vs2022/

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

ID: b92e9376-e663-c07a-6091-6d700e20fbf9
Version Independent ID: bde516e6-2e34-72f0-2195-0d7124d2994b
Content: Deploy to Azure Container Apps using Visual Studio
Content Source: articles/container-apps/deploy-visual-studio.md
Service: container-apps
GitHub Login: @alexwolfmsft
Microsoft Alias: alexwolf

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

Thank you for mentioning this - it will be addressed shortly in an upcoming PR.
#please-close

authors: DerekHerman-MSFT alexwolfmsft pseabury


text:
Clarification on Assignments

Is it possible to assign EnrollmentReader and EA purchaser to a SPN? When attempting to assign this at the billing account level I get the following response:
{"code":"Conflict","message":"The role assignment conflicts with an existing role assignment."}
I've tried using unique billingRoleAssignmentName for both using (new-guid) but no luck. Any help would be appreciated.

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

ID: 18b4787e-1e2f-dd28-b33b-0a220ad0819d
Version Independent ID: c663cfb2-3ea6-4a6e-9d88-f146526ead59
Content: Assign roles to Azure Enterprise Agreement service principal names
Content Source: articles/cost-management-billing/manage/assign-roles-azure-service-principals.md
Service: cost-management-billing
Sub-service: billing
GitHub Login: @bandersmsft
Microsoft Alias: banders

@jzuchora87 Thank you for feedback. We are actively looking into it. We will share updates soon.

We got same problem. Hope it will be fixed soon

@jzuchora87
@Dushelov
Hi There. An SPN can have only one role. I'll update the article to say that.
https://github.com/MicrosoftDocs/azure-docs-pr/pull/205385
For your situation, the EA Purchaser role is has all the permissions of the EA Reader role. We suggest that you assign the EA Purchaser role to your SPN.
#please-close

authors: Dushelov ShaikMaheer-MSFT bandersmsft jzuchora87


text:
URL links are broken

URL links are broken
Most of the links does not work in this page:
Manual training
Feature Tables
Feature Store
Model registry
MLFlow tracking
(not checked all of them)
Please check and correct. Thx.

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

ID: b8f41568-e2b1-2f7f-62f8-d63d230ba5d9
Version Independent ID: b697ab11-568c-6f00-1abb-80da3023cf62
Content: What is Databricks Machine Learning?
Content Source: databricks/scenarios/what-is-azure-databricks-ml.md
Service: azure-databricks
GitHub Login: @leifbro
Microsoft Alias: saperla

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

@csokaakos
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.
@leifbro
Please review this issue and update as appropriate.

Thanks for providing feedback that helps improve our documentation. This issue has been resolved. All of the links on this page have been fixed and verified that they're working. We are closing the issue.
#please-close

authors: Naveenommi-MSFT SaibabaBalapur-MSFT csokaakos kateglee-db


text:
Typo "Azure DB"→"Azure Database"

https://learn.microsoft.com/en-us/azure/dms/tutorial-azure-postgresql-to-azure-postgresql-online-portal?source=recommendations
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dms/tutorial-azure-postgresql-to-azure-postgresql-online-portal.md
#PingMSFTDocs

Looks good; thanks, @hyoshioka0128


text:
Update faq.yml

Update retention policy

@mrbullwinkle
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


text:
Update how-to-create-azure-support-request.md

Add minimal text to explain how to add a support plan using access ID and contract ID and limited support plans are hidden when they expire or run out of support incidents. Changes in Partner signature support will require a manual add of the support contract from July and it is hard to find where you add a suppot contract in azure. Most portals include a way to add in the create request workflow - except azure. Impacts 166k support incidents.  Feel free to contact acussons for more information. Previously discussed with John Lou.

@JnHs
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

Thanks @jnhs. I committed your suggestions.
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.

Thanks @Court72!
#sign-off

authors: AndrewMCussons Court72 JnHs