profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/PRMerger18/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

dotnet/docs 2846

This repository contains .NET Documentation.

Azure/MachineLearningNotebooks 2659

Python notebooks with ML and deep learning examples with Azure Machine Learning Python SDK | Microsoft

MicrosoftDocs/architecture-center 1334

Azure Architecture Center

MicrosoftDocs/ai-fundamentals 693

Code samples for AI fundamentals

MicrosoftDocs/azure-devops-docs 488

This repo is the home of the official Azure DevOps documentation for Microsoft. GitHub Issues filed in this repository should be for problems with the documentation.

dotnet/dotnet-api-docs 305

.NET API reference documentation (.NET Framework, .NET Core, .NET Standard and Xamarin)

MicrosoftDocs/appcenter-docs 98

content repo for Visual Studio App Center on docs.microsoft.com

dotnet/docs-desktop 68

This repository contains .NET documentation related to Windows Forms (winforms) and Windows Presentation Foundation (WPF).

MicrosoftDocs/azure-dev-docs 50

Public repo for Azure developer SDK documentation

MicrosoftDocs/AdaptiveCards 44

Docs for Adaptive Cards

pull request commentMicrosoftDocs/azure-docs

remove duplicated word

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

snowei

comment created time in 12 hours

issue closedMicrosoftDocs/azure-docs

North and West Europe Gateway IP Address Subnets Incorrect

Hi,

The Gateway IP Address Subnets listed for the Azure SQL Gateways in North and West Europe don't match the currently assigned IP addresses.

North Europe Gateway IPs - 40.113.93.91, 52.138.224.1, 13.74.104.113 North Europe Gateway Subnets - 13.69.233.136/29, 13.74.105.192/29, 52.138.229.72/29

West Europe Gateway IPs - 40.68.37.158, 104.40.168.105, 52.236.184.163 West Europe Gateway Subnets - 104.40.169.32/29, 13.69.112.168/29, 52.236.184.32/29

None of the assigned IP addresses fall into the provided subnets, which means we can't use the ranges for firewall rules.

Thanks,

Chris Simmons


Document Details

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

closed time in 13 hours

ZeroRows

PR closed MicrosoftDocs/azure-docs

Update generate-sas-tokens.md do-not-merge
+1 -1

1 comment

1 changed file

laujan

pr closed time in 13 hours

pull request commentMicrosoftDocs/azure-docs

Update generate-sas-tokens.md

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

laujan

comment created time in 13 hours

pull request commentMicrosoftDocs/sdk-api

Added information about timeout from WaitForXXXObject

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

arobincaron

comment created time in 13 hours

pull request commentMicrosoftDocs/azure-docs

Update generate-sas-tokens.md

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

laujan

comment created time in 13 hours

pull request commentMicrosoftDocs/cpp-docs

Repo sync for protected CLA branch

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

opbld16

comment created time in 19 hours

pull request commentMicrosoftDocs/SupportArticles-docs

Add note for GP Central Store

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

tom-maher

comment created time in 21 hours

pull request commentMicrosoftDocs/visualstudio-docs

Repo sync for protected CLA branch

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

ghogen

comment created time in 2 days

pull request commentMicrosoftDocs/azure-docs

Update release date

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

VanMSFT

comment created time in 2 days

pull request commentMicrosoftDocs/azure-docs

Update availability-group-manually-configure-tutorial.md

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

setanike-msft

comment created time in 2 days

pull request commentMicrosoftDocs/cpp-docs

Repo sync for protected CLA branch

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

opbld17

comment created time in 2 days

issue closedMicrosoftDocs/azure-docs

Indoor Maps API did not work, it is now using unsupported API for FeatureState

The example code did not work for updating the feature state in Indoor Maps. The Indoor maps 1.0 API is now deprecated. "The Azure Maps Creator services (Preview) version 1.0 will retire on 6 September 2021. Please transition to using version 2.0 by that date. For details, see Azure Maps Creator V1 Retirement." Ref: [(https://azure.microsoft.com/en-us/updates/azure-maps-creator-v1-will-be-retired-on-6-september-2021/)]

The following example code should be updated to a PUT and using the version 2.0 API with form:

                        var response = await httpClient.PostAsync(
                            $"https://atlas.microsoft.com/featureState/state?api-version=1.0&statesetID={statesetID}&featureID={featureID}&subscription-key={subscriptionKey}",
                            new StringContent(postcontent.ToString()));

Example using version 2.0 of the API:

                        var response = await httpClient.PutAsync(
                            $"https://us.atlas.microsoft.com/featurestatesets/{statesetID}/featureStates/{featureID}?api-version=2.0&subscription-key={subscriptionKey}",
                            new StringContent(postcontent.ToString()));

Document Details

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

closed time in 2 days

jpocloud

issue closedMicrosoftDocs/azure-docs

Replica-set membership: docs enhancement

The information around the replica-set size in different parts of the High availability | CosmosDb docs is vague/contradicting, which can be confusing/misleading to users.

Is there a chance that this is clarified? Or if it's considered too low level for this doc should there be a link to the Global distribution under the hood docs that goes deeper in the topic?

Details

In the start of the document is stated:

... Azure Cosmos DB maintains 4 replicas of data within a region.

which probably infers to a replica-set size of exactly 4.

Later on:

If your Azure Cosmos account is distributed across N Azure regions, there will be at least N x 4 copies of all your data.

which probably infers to a replica-set size of at least 4.

More details

In reality what (we think) is true is mentioned in the Global distribution under the hood docs:

The replica-set membership N is dynamic – it keeps fluctuating between NMin and NMax based on the failures, administrative operations, and the time for failed replicas to regenerate/recover.

This can be verified with a simple client.ReadAccountAsync() (tested using the latest C# v3 SDK) where in our case we get a replica-set between 3 and 4 nodes under normal operation (no failover)

  ...
  "userReplicationPolicy": {
      "asyncReplication": false,
      "minReplicaSetSize": 3,
      "maxReplicasetSize": 4
  },
  "systemReplicationPolicy": {
      "minReplicaSetSize": 3,
      "maxReplicasetSize": 4
  },

Document Details

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

closed time in 2 days

spygi

pull request commentMicrosoftDocs/azure-docs

removed extra `the` under Load Balancing rules

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

ZER-0-NE

comment created time in 2 days

pull request commentMicrosoftDocs/power-automate-docs

Update dynamics365-rpa-overview.md

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

lanlanlee2008

comment created time in 2 days

pull request commentMicrosoftDocs/windows-uwp

Update Windows 11 snap layouts documentation

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

epapa

comment created time in 3 days

pull request commentMicrosoftDocs/azure-docs

Added limit 20 for managed data flow IR

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

ssabat

comment created time in 3 days

pull request commentMicrosoftDocs/azure-docs

Provided context around why Key Vault Splitting

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

xximjasonxx

comment created time in 3 days

issue closedMicrosoftDocs/azure-docs

Supported RHEL version for Qualys extension

[Enter feedback here] According to Qualys ref doc: up to RHEL 8.3 is supported (https://www.qualys.com/docs/qualys-cloud-agent-getting-started-guide.pdf)

However, this Microsoft reference doc is not updated (still showing upto RHEL 8.1 is supported).

Hence, can you please update supported RHEL version for Qualys extension?


Document Details

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

closed time in 3 days

sreza-msft

issue closedMicrosoftDocs/azure-docs

Cannot find "Firewalls and virtual networks" screen in Synapse workspace

I just created a very basic Synapse Analytics setup consisting of just a StorageV2 storage account and a Synapse workspace.

For this setup, I cannot find the "Firewalls and virtual networks" screen as shown in the little screenshot -- which is partly caused by the zoom of the screenshot which doesn't show the menu bar on the left.

I suggest either

  1. providing more information, e.g. by including the menu bar in the screenshot, or just by text
  2. in case the article doesn't apply to basic setups such as mine described above, clarifying for which cases the article is relevant.

Document Details

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

closed time in 3 days

leonpeeters

issue closedMicrosoftDocs/azure-docs

wrong hyperlink

image

Hyperlink for the text: "Install Azure IoT Edge for Linux on Windows" redirects to "Install and manage Azure IoT Edge with Windows containers" instead of linux.

Probably should be linking to "https://docs.microsoft.com/en-us/azure/iot-edge/how-to-install-iot-edge-on-windows?view=iotedge-2018-06&tabs=powershell" instead.


Document Details

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

closed time in 3 days

Heidern89

pull request commentMicrosoftDocs/windowsserverdocs

Update rds-vdi-recommendations-2004.md

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

RAJU2529

comment created time in 3 days

pull request commentMicrosoftDocs/azure-devops-docs

Update sample-test-summary-trend.md

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

Anubhav-gangwal

comment created time in 3 days

pull request commentMicrosoftDocs/azure-devops-docs

Update sample-test-analyics-test-duration-trend.md

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

Anubhav-gangwal

comment created time in 3 days

pull request commentMicrosoftDocs/cpp-docs

Clarify int main(void) example

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

workingjubilee

comment created time in 4 days

pull request commentMicrosoftDocs/azure-docs

Update concepts-features.md

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

jeffmend

comment created time in 4 days

pull request commentMicrosoftDocs/azure-docs

removal of TLS inspection

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

cshea15

comment created time in 4 days

pull request commentMicrosoftDocs/win32

Correct a typo: availavble -> available.

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

dwainbunker

comment created time in 4 days

pull request commentMicrosoftDocs/dataexplorer-docs

Repo sync for protected CLA branch

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

shsagir

comment created time in 5 days