#StackBounty: #azure #azure-cognitive-search #azure-cognitive-services How to get PII Entities for non-text field in Azure search

Bounty: 100

I’ve created a Azure search Blob Index whose model looks somewhat like the below JSON on search

"value": [
        {
            "@search.score": 1,
            "metadata_storage_content_type": "application/octet-stream",
            "masked_text": null,
            "language": "en",
            "content": {
                "botName": "*****",
                "date": "*****",
                "channel": "******",
                "userid": "******",
                "conversationid": "*******",
                "isConversationIncomplete": false,
                "location": "",
                "locale": "",
                "messages": [ {
                        "date": "*****",
                        "isfromuser": "true",
                        "message": "Hi",
                        "sentiment": "positive",
                        "intent": "***** Intent",
                        "isConversationIncomplete": "false",
                        "id": "***"
                    },
                    {
                        "date": "****",
                        "isfromuser": "true",
                        "message": "My number is 999******",
                        "sentiment": "positive",
                        "intent": "***** Intent",
                        "isConversationIncomplete": "false",
                        "id": "****"
                    }]
            },
            "pii_entities": []
        }

I also want to create a PII detection skill for each message in the messages array, you can see the skill config in the image below

enter image description here

the problem is that I’m not able to change the Input value to any property from the result entity, it allows only the values as "languageCode" or "text" how can I create the PII skill for a input of my choice?


Get this bounty!!!

#StackBounty: #node.js #azure #vue.js #deployment Azure Web Service Deployment fails for Node.js project

Bounty: 50

I have a weird problem while deploying our Vue.js project to an Azure Web Service. First things first: the setup worked out perfectly and I can access the Web Service, the only problem I face is, that the deployment fails. When I locally start the application with npm run serve everything works fine, BUT I get tons of errors like 82:18 Property 'load' does not exist on type 'Vue'..

We ignored those errors for now, since load exists and we can use it normally and did not find a solution to resolve those errors. Therefore, the question is: might those errors (even though the displayed errors are flagging something we use and which works) fail the deployment?

The last line of the deployment is as follows:

2021-06-23T15:09:46.095Z - npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.1 (node_modules/webpack/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/webpack-dev-server/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/watchpack-chokidar2/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.1 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/fork-ts-checker-webpack-plugin/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

-  Building for production...
 ERROR  Build failed with errors.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! project@0.1.0 build: `vue-cli-service build`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the project@0.1.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/.npm/_logs/2021-06-23T15_09_29_048Z-debug.log
/opt/Kudu/Scripts/starter.sh oryx build /home/site/repository -o /home/site/wwwroot --platform nodejs --platform-version 14 -i /tmp/8d93658061b46ee -p compress_node_modules=tar-gz --log-file /tmp/build-debug.log 

I honestly do not know what to do with this huge error. I searched around a bit, but did not find a fitting solution.


Get this bounty!!!

#StackBounty: #azure #vue.js #azure-devops #azure-pipelines #vue-cli Can VUE CLI Run on be run/installed on Azure Pipelines?

Bounty: 100

I currently have our backend project running on azure pipelines and I would love to integrate our front-end VUE project in the same way. However, I have tried everything to get vue-cli-service installed/built on our pipeline to no avail. The same exact build commands work locally but will not work on the Azure VM. Our pipeline yaml file currently looks like this:

YAML

    trigger:
- main
pool:
  vmImage: 'ubuntu-latest'
steps:
- task: NodeTool@0
  inputs:
    versionSpec: '10.12'
  displayName: 'Install Node.js'
- script: |
    npm install -g @vue/cli@latest
    npm i -g @vue/cli-service-global
    npm install
    npm run build
    yarn global add @vue/cli && yarn build
    vue serve
  displayName: 'npm install and build'

As you can see I have tried various methods to get vue-cli installed/built but I get the same error every time:

The Output:

yarn global v1.22.10
[1/4] Resolving packages...
warning @vue/cli > @vue/cli-shared-utils > request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
warning @vue/cli > @vue/cli-shared-utils > @hapi/joi@15.1.1: Switch to 'npm install joi'
warning @vue/cli > @vue/cli-shared-utils > request > har-validator@5.1.5: this library is no longer supported
warning @vue/cli > @vue/cli-shared-utils > request > uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
warning @vue/cli > @vue/cli-shared-utils > @hapi/joi > @hapi/hoek@8.5.1: This version has been deprecated and is no longer supported or maintained
warning @vue/cli > @vue/cli-shared-utils > @hapi/joi > @hapi/topo@3.1.6: This version has been deprecated and is no longer supported or maintained
warning @vue/cli > @vue/cli-shared-utils > @hapi/joi > @hapi/topo > @hapi/hoek@8.5.1: This version has been deprecated and is no longer supported or maintained
warning @vue/cli > @vue/cli-shared-utils > @hapi/joi > @hapi/bourne@1.3.2: This version has been deprecated and is no longer supported or maintained
warning @vue/cli > @vue/cli-shared-utils > @hapi/joi > @hapi/address@2.1.4: Moved to 'npm install @sideway/address'
warning @vue/cli > @vue/cli-ui > apollo-server-express > graphql-tools > uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
warning @vue/cli > globby > fast-glob > micromatch > snapdragon > source-map-resolve > resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
warning @vue/cli > globby > fast-glob > micromatch > snapdragon > source-map-resolve > urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Installed "@vue/cli@4.5.13" with binaries:
      - vue
Done in 16.68s.
yarn run v1.22.10
$ vue-cli-service build
/bin/sh: 1: vue-cli-service: not found
error Command failed with exit code 127.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Failed to locate entry file in /home/vsts/work/1/s.
Valid entry file should be one of: main.js, index.js, App.vue or app.vue.

There's a package.json in the current directory.
Did you mean yarn serve?
##[error]Bash exited with code '1'.
Finishing: npm install and build

The Error:

$ vue-cli-service build
/bin/sh: 1: vue-cli-service: not found
error Command failed with exit code 127.

package.json

{
  "name": "test-vue",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "serve": "vue-cli-service serve",
    "build": "vue-cli-service build",
    "lint": "vue-cli-service lint"
  },
  "dependencies": {
    "@fortawesome/fontawesome-svg-core": "^1.2.18",
    "@fortawesome/free-brands-svg-icons": "^5.8.2",
    "@fortawesome/pro-light-svg-icons": "^5.8.2",
    "@fortawesome/pro-regular-svg-icons": "^5.8.2",
    "@fortawesome/pro-solid-svg-icons": "^5.8.2",
    "@fortawesome/vue-fontawesome": "^0.1.6",
    "add": "^2.0.6",
    "axios": "^0.18.0",
    "bootstrap": "^4.3.1",
    "chart.js": "^2.8.0",
    "core-js": "^2.6.5",
    "moment": "^2.24.0",
    "node-sass": "^4.12.0",
    "popper.js": "^1.15.0",
    "v-calendar": "^1.0.0-beta.16",
    "vee-validate": "^2.2.11",
    "vue": "^2.6.10",
    "vue-chartjs": "^3.4.2",
    "vue-class-component": "^7.0.2",
    "vue-directive-tooltip": "^1.6.2",
    "vue-popperjs": "^2.0.4",
    "vue-router": "^3.0.6",
    "vuex": "^3.0.0",
    "vuex-class": "^0.3.2",
    "vuex-module-decorators": "^0.9.9",
    "webpack": "4.0.0",
    "yarn": "^1.16.0"
  },
  "devDependencies": {
    "@vue/cli-plugin-babel": "^3.7.0",
    "@vue/cli-plugin-eslint": "^3.7.0",
    "@vue/cli-plugin-typescript": "^3.7.0",
    "@vue/cli-service": "^3.7.0",
    "@vue/eslint-config-typescript": "^4.0.0",
    "babel-eslint": "^10.0.1",
    "eslint": "^5.16.0",
    "eslint-plugin-vue": "^5.0.0",
    "sass": "^1.20.1",
    "sass-loader": "^7.1.0",
    "ts-loader": "^6.0.1",
    "typescript": "3.4.5",
    "vue-property-decorator": "^8.1.1",
    "vue-template-compiler": "^2.5.21"
  },
  "eslintConfig": {
    "root": true,
    "env": {
      "node": true
    },
    "extends": [
      "plugin:vue/essential",
      "eslint:recommended",
      "@vue/typescript"
    ],
    "rules": {},
    "parserOptions": {
      "parser": "@typescript-eslint/parser"
    }
  },
  "postcss": {
    "plugins": {
      "autoprefixer": {}
    }
  },
  "browserslist": [
    "> 1%",
    "last 2 versions"
  ]
}

I believe the issue is related to the script vue-cli-service build


Get this bounty!!!

#StackBounty: #windows #powershell #azure #group-policy #applocker Dynamic Windows 10 AppLocker rules for user groups not working

Bounty: 100

I’m trying to make dynamic app blocking rules with AppLocker. The setup is that I have predefined AppLocker rules (for example, Allow windows user group 'Chrome' access 'chrome.exe' (not actual group name or actual path)) and then assigned users to groups at login with the help of a Windows service.

That worked fine at first, but after a while it stopped (AppLocker itself worked, but user groups specific rules didn’t apply–in other words, everything was blocked). I tested all policies combined via PowerShell commandlets, and according to them the user that belongs to the user group Chrome should be allowed to access chrome.exe, but in reality I’d get an app blocked prompt.

Then I tried creating user specific rule to allow chrome.exe, which worked fine and as soon as I removed it (group rule still exists), I’d get blocked again. Or even just changing existing user group policy to point to specific user made it work and then changing back to point to user group not work again.

Funny part – after a few VM restarts it worked again, and then next day when I wanted to demo it to a colleague, I got the same issue again, which again was solved by multiple VM restarts.

An obvious possible issue could be ‘does the user really belong to the group?’ and the answer is yes: each time when the policy wouldn’t work, I’d go into lusrmgr and verify that.

For additional context – the VM is hosted on Azure, running Windows 10 multi-session 21H1, AppLocker is setup on local machine level (no domain wide policies or anything like that atm).


Get this bounty!!!

#StackBounty: #azure #windows-10 #applocker Windows 10 AppLocker rules for user groups stop working randomly

Bounty: 100

I’m playing around trying to make sort of dynamic app blocking with help of applocker. The setup is that I have predefined applocker rules (For example Allow windows user group 'Chrome' access 'chrome.exe' (not actual group name or actual path)) and then basically assigning user to groups on login with a help of a windows service.

And that worked fine at first, but after a while it stopped (applocker itself worked, but user groups specific rules didn’t apply, in other words everything was blocked). I tested all policies combined via powershell commandlets and according to them the user that belongs to the user group Chrome should be allowed to access chrome.exe, but in reality I’d get app blocked prompt.

Then I tried creating user specific rule to allow chrome.exe which worked fine and as soon as I removed it (group rule still exists) I’d get blocked again. Or even just changing existing user group policy to point to specific user made it work and then changing back to point to user group not work again.

Funny part – after a few vm restarts it worked again and then next day when I wanted to demo it to a colleague I got same issue again which again was solved by multiple vm restarts.

Obvious possible issue could be ‘Does the user really belong to the group?’ and the answer is yes, each time when the policy wouldn’t work I’d go into lusrmgr and verify that.

For additional context – VM is hosted on Azure, running Windows 10 multi-session 21H1, AppLocker is setup on local machine level (no domain wide policies or anything like that atm)


Get this bounty!!!

#StackBounty: #azure #azure-web-app-service #azure-sql-database #azure-virtual-network Azure Web App connecting to SQL FO Group over Pr…

Bounty: 100

I would like to know few things about my web apps hosted in Central US connecting to Azure SQL FO group connection string. The Primary SQL is hosted in the same region which is Central US and the Secondary Replica is hosted in East US 2.
I am considering using Private Link for Azure SQL.So in order for my web app to talk to the Azure SQL over the private endpoint, i have to enable regional VNET integration for my Web App as i read in MS Docs.
So at the moment i have two subnets in Central US and one of the subnets i have to dedicate for creating VNET integration for my Web Apps. The other subnet will be hosting my SQL Private Endpoint.
I have already enabled Global VNET peering between Primary Central US and the Secondary VNET in East US 2.
So i would like to know whether during a disaster and after a failover happens for my SQL from Primary Central US to secondary East US 2, will my Web Apps automatically connect to the SQL FO group read/write listener after i enable private link for my Azure SQL.
I don’t understand what it means by this below as per the link :

https://docs.microsoft.com/en-us/azure/architecture/example-scenario/private-web-app/private-web-app

Global peering
Any service in any Azure region that can connect through the Virtual Network can reach the database’s private endpoint, for example through Virtual Network peering in hub-and-spoke topologies. However, for App Service regional VNet Integration, the peered Virtual Networks must be located in the same Azure region.

As per the line "However, for App Service regional VNet Integration, the peered Virtual Networks must be located in the same Azure region.", my peered virtual network is from Central US to East US 2 which is like Global Peering.
So how this statement applies to in my case.

Looking forward to some pointers


Get this bounty!!!

#StackBounty: #.net #azure #azure-functions #azure-web-app-service Dynamically Adjust System Time of Azure App Service

Bounty: 50

We have an Azure Function (dotnet) deployed that relies heavily on the current date/time for many operations.

We are writing an integration test suite for it and would really love to keep a blackbox approach. That is, we’d rather not internally mock the date/time if possible.

Is there a way to adjust the system time of the app service to achieve this? Ideally, there would be a non-intrusive way to achieve this, but I’m open to lightly-instrusive options


Get this bounty!!!

#StackBounty: #azure #azure-data-factory #azure-pipelines-yaml Using Azure Data Factory utilities to generate ARM Template does not gen…

Bounty: 100

When using the "publish" on the Azure Data Factory the ARM Template is generated

        "name": "[parameters('factoryName')]",
        "type": "Microsoft.DataFactory/factories",
        "apiVersion": "2018-06-01",
        "location": "[parameters('dataFactory_location')]"

When I use the NPM task in my build pipeline (@microsoft/azure-data-factory-utilities) it generates the following:

        "name": "[parameters('factoryName')]",
        "type": "Microsoft.DataFactory/factories",
        "apiVersion": "2018-06-01",
        "properties": {}

Running the process on my local machine has the same results (invalid ARM template)

So currently creating the ARM template via the CI/CD pipeline does not create a valid ARM template.

I have followed these instructions to get it going in my pipeline https://docs.microsoft.com/en-us/azure/data-factory/continuous-integration-deployment-improvements

Any suggestions or pointers would be very welcome.


Get this bounty!!!

#StackBounty: #azure #active-directory #azure-data-factory #azure-data-factory-2 Azure data factory AD access token using certificate

Bounty: 50

How to get access token from AAD authentication service using certificate in Azure data factory web activity , I can not use client secret for this , Certificate from Service principle is already stored in Azure key vault

My ADF pipeline flow is like thuis

1)Web activity to point to the certificate stored in keyvalut
2)web activity url as https://login.microsoftonline.com//oath2/token
and in body
@concat(‘grant_type=client_credentials&client_id=’,,’&client_assertion=’,activity(‘Web1′).output.cer,’&client_assertion_type=’,’urn:ietf:params:oauth:client-assertion-type:jwt-bearer’,’&resource=’,’https://analysis.windows.net/powerbi/api’)

Getting error as

Invoking Web Activity failed with HttpStatusCode – ‘NotFound’, message – ‘The requested resource does not exist on the server. Please verify the request server and retry’


Get this bounty!!!